Default runtimeCaching strategies not ideal?

[mrumm]

I had some undesirable behaviour when users are submitting a change to the backend and then navigate to a different page that shows same backend content. Outdated cache of the service worker was the issue, i.e. service worker cached .json content for the page was served instead of making a new request to the network to fetch updated content as I would expect with SSR and seems default next js behaviour without next-pwa installed.

I find following strategy not ideal for pages that are SSR in cache.js:

{
    urlPattern: /\/_next\/data\/.+\/.+\.json$/i,
    handler: 'StaleWhileRevalidate',
    options: {
      cacheName: 'next-data',
      expiration: {
        maxEntries: 32,
        maxAgeSeconds: 24 * 60 * 60 // 24 hours
      }
    }
},

Instead of handler 'StaleWhileRevalidate', I was able to avoid above issues use the handler 'NetworkFirst' instead:

{
    urlPattern: /\/_next\/data\/.+\/.+\.json$/i,
    handler: 'NetworkFirst',
    options: {
      cacheName: 'next-data',
      expiration: {
        maxEntries: 32,
        maxAgeSeconds: 24 * 60 * 60 // 24 hours
      }
    }
},

Should 'NetworkFirst' be the default for the urlPattern //_next/data/.+/.+.json$/i or at least for all SSR pages?