Users need a way to declare npm dependencies in their custom plugins so they can avoid merge conflicts when the root level package.json changes (which is at least every time we do a version bump). Subdirectory package.json files are supported with npm, but it requires cding into the directory to run the npm commands. So the CLI will need to scan each plugin dir for a package.json and then run npm install if one exists.
It would also be great to be able to add/update packages in a plugin's package.json via reaction-cli without having to manually cd into the directory. Not sure how gnarly that command would look (probably pretty long), but I think it's at least worth investigating.
Users need a way to declare npm dependencies in their custom plugins so they can avoid merge conflicts when the root level package.json changes (which is at least every time we do a version bump). Subdirectory package.json files are supported with npm, but it requires
cd
ing into the directory to run thenpm
commands. So the CLI will need to scan each plugin dir for a package.json and then runnpm install
if one exists.It would also be great to be able to add/update packages in a plugin's package.json via
reaction-cli
without having to manuallycd
into the directory. Not sure how gnarly that command would look (probably pretty long), but I think it's at least worth investigating.