Alexander Mills
Alexander Mills
if we have: ``` root/ foo/ bar/ baz/ ``` if we run `nlu run` in the root dir, it should search for .nlu.json files in all dirs, with depth 3...
If an .nlu.json file contains `searchable: false` then stop searching in that dir
we won't search below --search-floor so if `--search-floor=/home/oleg/foo/bar` we would never search below that dir
when running ```bash nlu run ``` in the npm-link-up project itself, we see: ``` nlu/warn: The following packages could not be located: nlu/warn: [ 'frankenstop', 'freeze-existing-props', 'suman-browser', 'sce-plugins', 'sce-plugin-typings', 'suman-inquirer',...
`nlu --which` or `nlu run --which` or `nlu run --which -c xyz` the --which flag logs the path of .nlu.json file that would be used
if we get this: ``` { "packages":{ "foo": [], "bar": [] } } ``` we should map it to: ``` { "packages":{ "foo": { "list": []}, "bar": { "list": []},...
when running nlu run, we should exclude packages from being linked nlu --exclude="foo,bar" nlu --exclude-completely="foo,bar" exclude-completely means x won't be linked to y, whereas just exclude means x will be...
``` { "searchRoots": [], // relative to location of .nlu.json file "umbrella":true, "list": [], "exclude":[] } ``` if you then run: `nlu run` it will pick up the above file,...
if nlu run is run on a project w/o an .nlu.json it's basically a no-op. Currently it exits with code 1. But perhaps if we use ```bash nlu run --ignore-missing-config...
Make it work if packages aren't already published to NPM? verdaccio? https://stackoverflow.com/questions/51888198/skip-install-for-particular-dep Is there a way to run npm install but skip a particular dependency? Something like: ```bash npm install...