npm-link-up icon indicating copy to clipboard operation
npm-link-up copied to clipboard

:arrows_counterclockwise: Link your NPM projects automatically, for sophisticated / modular local development.

Results 31 npm-link-up issues
Sort by recently updated
recently updated
newest added

> Special note: If you cannot add .nlu.json files to the packages b/c maybe your people are picky, there is a way to just use an nlu.umbrella.json file. File a...

what are --shell-version and --install-main for as in ``` nlu run --shell-version --install-main; ```

on macos and *nix? /usr/local/etc/bash_completion.d

nlu final map should work with --umbrella opt

Use --every for zero config --all will work with packages with .nlu.json as the entrypoints --every will work for every package, even those without .nlu.json files

--all does all packages within the top level search root (by default cwd) --every links every package in the searchRoots to every other package

check if dupe package names in same folder cause issues - write a test that should capture this problem, only resolution is to ignore the path/folder that contains the dupe...

if you run `$ nlu ls`, it will show a visual of all the symlinks in the projects

if version in package.json is not the same, but it's a symlink, we should ignore the discrepancy determineIfReinstallIsNeeded

in `$HOME/.nlu/global-settings`, or what not ```js { "packages": { "suman":{ "list": [] }, "suman-utils":[ "list": [] ] } } ```