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

npm-link-watch

v1.0.26

Published

This command line is to solve the problem of `npm/yarn link`: the linked package has its own `node_modules`, which results in a lots of issues relate to dupplicate modules.

Downloads

21

Readme

This command line is to solve the problem of npm/yarn link: the linked package has its own node_modules, which results in a lots of issues relate to dupplicate modules.

Similar to npm link or yarn link but instead of symlink the entire package, npm-link-watch watch and sync specific directories/files inside the package.

How to use

Use it similar to npm/yarn link:

# Run at package `x`:
npx npm-link-watch ./lib

# Run at the project that has `x` as a dependency:
npx npm-link-watch x
# --> a watcher will watch and sync `x/lib` to `<current_project>/node_modules/x/lib`.

Your machine already has npx if you installed NodeJS version 6 or newer. In case you don't want to type npx all the time, run npm install -g npm-link-watch npm-unlink-watch

Notice: If your package has just installed new dependencies, you then have to install those dependencies into your project as well.

API

npx npm-link-watch <...path>

  • ...path: strings of relative paths (start with ./), separated by space.

    Save symbolic links of the specified paths into a global directory (~/.npm-link-watch). Run at the package you want to link and watch

npx npm-link-watch <...package-name>

  • ...package-name: strings of package names (exact string in package.json#name), separated by space.

    Start a watcher that watch and sync directories/files from package-name to <current_project>/node_modules/package-name. Run at the project that has package-name as an installed dependency.

npx npm-unlink-watch <...package-name>

  • ...package-name: strings of package names (exact string in package.json#name), separated by space.

    Remove the symbolic links saved by npx npm-link-watch <...path>. The comand also attempts to restore the synced content inside <current_project>/node_modules/package-name, but this may not consistent for all cases. For more consistent, you should run yarn install --force

LICENSE

MIT