It's becoming more and more of a pain to do development across multiple plugins as the number of NPM packages increase. Shrinkwrap has made this even more painful (see JENKINS-40206).

Goal: When developing Blue Ocean plugins and making changes in assocaited/dependency NPM packages, all changes would get auto-synchronized to everywhere needed without having to jump through NPM publish and install hoops for every change.

However, it seems impossible to avoid a proper npm publish and install cycle at the end of each "Dev Cycle". If we don't do that then we're going to be talking about some hokie local linking process for NPM deps, which would def just result in a slew of other weird issues and dodgy dependency defs. So, we need to make sure that it's not possible to release plugins that have locally linked/synch'd dependencies i.e. something that checks that all NPM deps are properly published etc before the maven release can happen.

Random thoughts:

• If changes are synched to one of the packages in node_modules, and the change is to the package.json, we do not perform that sync. Instead, the entirety of the source package needs to be re-installed because there may be new transitive dependencies that also need to be installed. So instead of syncing that one file change, we need to reinstall.