cacheable-response | HTTP compliant route path middleware for serving cache | Caching library

(Update: Workbox v5 makes the process of using a local copy of the Workbox runtime much simpler, and in most cases, it's the default.)

There's one more step that's required. The "Using Local Workbox Files Instead of CDN" has the details:

If you don’t want to use the CDN, it’s easy enough to switch to Workbox files hosted on your own domain.

The simplest approach is to get the files via workbox-cli's copyLibraries command or from a GitHub Release, and then tell workbox-sw where to find these files via the modulePathPrefix config option.

If you put the files under /third_party/workbox/, you would use them like so:

I have set long expiry cache headers on all files served from /workbox-v4.3.1/ path since it is versioned. Is there any downside to this approach?

There's no downside to that approach because, as you mention, the /v4.3.1/ path segment is used in your URL, so the content should never change. There is some nuance around whether or not URLs loaded via importScripts() (which happens for all of the Workbox URLs) are actually checked for updates, and that's detailed more in this article. But what you're doing with Cache-Control headers should be fine.

Can Workbox provide support for teams which don't use any bundlers?

That's straightforward with Workbox v5 (as of Nov. 2019, in pre-release), using generateSW with the following configuration:

This can happen due to multiple reason. Please check if the app itself is running any demon from within. What do you see when you run ps aux || grep node. If you can post your app.js or server.js or index.js or anything which acts as main file of your application file here that would help to diagnose the issue.

if you are setting any environment variable like production you can do it explicitly i.e export NODE_ENV=production

You can start the server.js app without npm with pm2 with below command pm2 start server.js -- --prod This should work without any problem.

For anything more than this i would recommend the pm2 config file this is the right way of using pm2 scripts.

We are actively working on a rewrite for the InjectManifest plugin that will perform a webpack child compilation on swSrc, in addition to populate the precache manifest.

https://github.com/GoogleChrome/workbox/issues/1513#issuecomment-506482323