lldeps v1.0.2

lldeps

package.json can contain local dependencies in this format file:../path/to/some/package.

When you run npm install, it copies that directory into node_modules. Hence, editing code in ../path/to/some/package won't reflect any changes in the master project.

To overcome this issue, run lldeps where package.json lives to npm link all local file dependencies.

I personally use this in large monorepo projects where I want to modularize large codebases into smaller ones for faster transpilation & unit testing times locally.

Usage

npm install -g lldeps
lldeps # run this in the directory where package.json exists