Better control of JS dependencies from NPM / JS standard tools
We currently bundle our JS dependencies in the repository. This makes life simpler from a development point of view, but makes it trickier to manage those dependencies, and means that we miss out on other good practices with JS, such as minification etc.
This isn't at all my field, and I suspect @nitarocc is best placed to make recommendations for how we should proceed with this.
One reason this is coming up now: it is easier to list the dependencies of JS if we have a lockfile/manifest, rather than pointing to the JS files themselves.