Deploying and updating front end database applications
It deserves all the byte-saving care and attention you would give to the assets served up by a production-grade web framework.
That means it should be minified, compressed, and most certainly includes source maps.
For right now, a bit of asset bundle splitting will speed up the experience for your users on every release.
Serve static applications from a content distribution network.
This unpredictable asynchronous behavior is part of why extra care has to be taken around versioning and releases. Assume that some users will be running older versions of the app, and be prepared to handle requests from deprecated features.
Consider releases as a continuum of changes and decide how long your release cycle is.
Once your build and testing process is independent of a server framework, it frees up the delivery process as well.
This allows clients to keep pointing at the same URL while maintaining caching semantics.
It also allows you to perform invalidations when you release code, despite the lack of asset fingerprinting.
The same approach is often used when releasing server side code, but the stakes are higher with statically hosted single page apps.
A gradual approach is crucial because rolling code back can only be as fast as your CDN’s invalidation period.
When you serve up a giant concatenated bundle, the client is forced to download everything fresh with every minor change, no matter how small it is.