npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

symlink-manager

v1.5.1

Published

Symlink Manager easily manage to symbolic link processes of your dependency packages.

Downloads

762

Readme

Symlink Manager easily manage to symbolic link processes of your dependency packages.

symlink-introducing

Installation & Usage

yarn add symlink-manager --dev

# or if you are using npm

npm install symlink-manager --save-dev

Insert the following line in scripts of your package.json file.

  // ...
  "scripts": {
    "symlink": "symlink",
    // ...
  },

Symlink-manager will help you for direction.

yarn symlink

# or if you are using npm

npm run symlink

| Command | Description | | ------- | ------------------------------------------------------------------- | | Link | Creates symbolic link for selected packages | | Unlink | Removes symbolic link for linked packages | | Copy | Copies link folder into node_modules directly without symbolic link |

Symlink-manager supports Angular. (Only supports created with ng generate lib libraries).

yarn symlink --angular

Symlink-manager supports Yarn.

yarn symlink --yarn

Symlink-manager can take your packages on command.

yarn symlink --packages my-package-1,my-package-2 --no-watch

Symlink-manager supports the CI

yarn symlink copy --angular --all-packages --no-watch --sync --excluded-packages package1,package2

If building order matters, you can pass --sync. You can pass --prod option for production configuration.

yarn symlink --sync

If you are not using Angular, you must add symlink.config.json for your configuration.

symlink.config.json example:

{
  "yarn": true,
  "packages": [
    {
      // required
      // your main dependency folder path. The folder must have package.json.
      "libraryFolderPath": "packages/core",
      // required
      // this folder for symbolic link. You may enter the same value as libraryFolderPath.
      // linkFolderPath folder must have package.json.
      "linkFolderPath": "dist/core",
      // optional
      // your build command.
      "buildCommand": "ng build core",
      // optional
      // output -> cd packages/core && ng build core
      "buildCommandRunPath": "packages/core",
      // optional
      // symlink-manager doesn't watch these folders
      "exclude": ["node_modules", "dist"]
    }
  ]
}

For more: See the Angular example project and document See the React example project and document

Without symlink-manager for Angular

  • After 5th step (Check the 5 steps in Angular Example), run ng build core --watch
  • Open new terminal window and go dist/core (cd dist/core)
  • Run npm link
  • Go back to main folder (cd ../../)
  • Run npm link @symlink/core

Repeat it for every package.

Do not forget, symlink-manager do this automatically. Symlink-manager can create symbolic link a lot of packages in one terminal window