Closed
Description
As more widgets convert, and as we are going to go whole hog on #104, we need to do a better job handling and building the amigo2 JS in the repo.
Things we'd like to accomplish here:
- all amigo "context" and data should be merged into /javascript/npm/amigo2 and have the application builder point there, so local installs will always have their own version
- the publicly pushed amigo2 npm should always be aligned with the public site, with separate semvar for the different branches
- all JS should be built and managed by a monolithic pipeline, no client namespace assumptions
- versioning should be much faster, automatic, and essentially increment on pushes
- remove need for "conflict" modified files to be generated during install