mvllow / next-pwa-template Goto Github PK

Awesome template! You might consider using Tailwind JIT for improved HRM performance (will be the default in the next major version)

On Next.js version 12, the service worker does not install and there is an error in the console:

Uncaught (in promise) bad-precaching-response: bad-precaching-response :: [{"url":"https://next-pwa-template.vercel.app/_next/server/middleware-manifest.json","status":404}]
    at Y.j (https://next-pwa-template.vercel.app/workbox-4a677df8.js:1:16755)
    at async Y.D (https://next-pwa-template.vercel.app/workbox-4a677df8.js:1:16353)
    at async Y.v (https://next-pwa-template.vercel.app/workbox-4a677df8.js:1:7595)

Would like to explore what differences (if any) the default create-next-app provide when using v11. This should include things like the conformance updates (lint rules and such) as well as showcasing the new next/script and improved next/image.

Hi, I actually was not able to implement next-pwa into my esm config alongside the bundle analyzer and axiom.

I looked at this template to solve the problem, but I was not able to get it working

import { withAxiom } from 'next-axiom'
import withBundleAnalyzer from '@next/bundle-analyzer'
import pkg from './next-i18next.config.js'
const { i18n } = pkg

// create the bundle analyzer config
const withMyBundleAnalyzer = withBundleAnalyzer({
  enabled: process.env.ANALYZE === 'true'
})

/**
 * Run `build` or `dev` with `SKIP_ENV_VALIDATION` to skip env validation.
 * This is especially useful for Docker builds.
 */
!process.env.SKIP_ENV_VALIDATION && (await import('./src/env.mjs'))

/** @type {import("next").NextConfig} */
const config = withMyBundleAnalyzer(
  withAxiom({
    reactStrictMode: true,
    i18n
  })
)
export default config