Angular: Setting maxAge on static content files

My Lighthouse Report suggests that I "Serve assets with an efficient cache policy". My problem is that my runtime.xxx.js, polyfills.xxx.js, main.xxx.js, and styles.xxx.js files need a longer cache lifetime than 1hr. Can a longer cache lifetime for these files be achieved using a Service Worker? If so, how?

I am using a ServiceWorker, which uses an ngsw-config file.

{
  "index": "/index.html",
  "assetGroups": [
    {
      "name": "app",
      "installMode": "prefetch",
      "resources": {
        "files": [
          "/favicon.ico",
          "/index.html"
        ],
        "versionedFiles": [
          "/*.bundle.css",
          "/*.bundle.js",
          "*.js",
          "/*.chunk.js"
        ]
      },
      "cacheConfig": {
        "maxSize": 100,
        "maxAge": "86400",
        "strategy": "performance"
      }
    },
    {
      "name": "assets",
      "installMode": "lazy",
      "updateMode": "prefetch",
      "resources": {
        "files": [
          "/assets/**"
        ]
      }
    }
  ]
}

When I use Google Chrome DevTools and go offline, my application still shows. The Network tab shows that my styles.xxx.css is "(from Service Worker)", but my runtime.xxx.js, polyfills.xxx.js, and main.xxx.js are "(from memory cache)". When I click on runtime.xxx.js the Headers tab cache-control is max-age=3600. (Perhaps a default header setting is overriding my Service Worker.)

I've included the information from the Chrome Dev Tools Network tab when the app is offline. And my files are in dist/maldonado-a/. For example dist/maldonado-a/polyfills.xxx.js.

Please write to me if you need more information. Thank you.

from Angular: Setting maxAge on static content files