webpack-dev-middleware VS offline-plugin

Are you using webpack? If so, they have a middleware for exactly this case: https://github.com/webpack/webpack-dev-middleware. The example there should be added to your express script with some form of conditional statement to use express.static in your deployment and webpack-dev-middleware in dev.

It looks like this should have been fixed back in 2017: https://github.com/webpack/webpack-dev-middleware/issues/229

Meteor-Webpack integrates webpack-dev-middleware and webpack-hot-middleware to benefit HMR in your project. The only thing you have to do is enabling this feature just like any other Webpack project;

For example, you have a Progressive Web Application using Service Workers, written in Angular, then you have to create a service worker manifest based on your output files. We don’t have a solution for this on Meteor CLI natively. However, Webpack has a lot of community plugins such as OfflinePlugin , Workbox and many others for this problem as a solution. Just install them, and add to your webpack.config.js . Meteor-Webpack will handle it like you’re working on a pure Webpack project.

Since Omatsuri is a browser only application the only thing that we need from service worker is to cache assets and provide app shell. Offline plugin does exactly that, the only thing we need to do – add it to the production build in webpack config: