@ducanh2912/[email protected]

Patch Changes

• #55 c8523d5 Thanks @DuCanhGH! - chore(deps): updated dependencies, moved webpack to "dependencies"

  • webpack is now a dependency rather than a peer dependency.
  • Reverted the change where we replaced webpack with Next's webpack instance.

@ducanh2912/[email protected]

Minor Changes

• #53 165f4c3 Thanks @DuCanhGH! - feat: use Next's webpack instead of importing a new one

  • next-pwa should now use Next's webpack instance to avoid having multiple webpack copies.

@ducanh2912/[email protected]

Patch Changes

• #49 b53cf03 Thanks @DuCanhGH! - fix(next-pwa): fixed build crashing when swcMinify is set to false

@ducanh2912/[email protected]

Patch Changes

• 4d13948 Thanks @DuCanhGH! - fix(next-pwa): fixed swc-minify crashing build when all swc sources can't be resolved

  • The new behaviour should be to use terser-webpack-plugin's terserMinify when they can't be found.
  • With this patch, @swc/core should now be preferred over next/dist/build/swc, which makes more sense than the old behaviour. You can now override the selected swc.

@ducanh2912/[email protected]

Patch Changes

• 33282e1 Thanks @DuCanhGH! - fix(next-pwa): fixed @swc/core not found

  • This is due to our change to terser-webpack-plugin's TerserPlugin.swcMinify, which tries to resolve @swc/core. It is not installed by default in our case.

@ducanh2912/[email protected]

Patch Changes

• #44 8feffa0 Thanks @DuCanhGH! - fix(next-pwa): fixed next-pwa not being minified properly

  • This is due to the change done in 9.1.0. I forgot to configure jsc.minify, so next-pwa was minified using the default options.

@ducanh2912/[email protected]

Minor Changes

• f68b11f Thanks @DuCanhGH! - feat(next-pwa): minify custom workers, sw-entry's workers and fallback workers using swc

  • next-pwa should now use swc instead of terser to minify these.

@ducanh2912/[email protected]

Patch Changes

• a47f236 Thanks @DuCanhGH! - fix(swc-loader): only log when both swc sources can't be resolved

  • Previously, swc-loader used to always log "Using @swc/core to compile next-pwa's features. Please install it if you haven't." if next/dist/build/swc can't be resolved. This can get annoying, so this changes it so that it only logs when both sources can't be resolved.

• 8cb59af Thanks @DuCanhGH! - chore(next-pwa): removed app/_offline/page.js auto-detect for offline fallbacks

  • A part of v9's breaking changes.

@ducanh2912/[email protected]

Major Changes

• #38 7bd3ba7 Thanks @DuCanhGH! - BREAKING CHANGE(next-pwa, next-sw): use Next's swc bindings instead of @swc/core

  What: From now on we will try to resolve next/dist/build/swc in swc-loader (needed to use cacheOnFrontEndNav, custom workers and offline fallbacks). If it can't be resolved, we will fallback to @swc/core (needed to be installed manually).

  Why: This is to save disk space (we don't need two @swc/core) and avoid exceeding Vercel's serverless size limit.

  Why use Next's next/dist/build/swc: it seems that @next/mdx is also doing the same for their mdx Rust compiler.

  How to upgrade: Usually you don't need to do anything (if you are on Next 12.0.0 or later). But if you see this line when you build your Next app: Using @swc/core to compile next-pwa's features. Please install it if you haven't. or Failed to resolve swc. Please install @swc/core if you haven't., please do as instructed.

• #38 7bd3ba7 Thanks @DuCanhGH! - BREAKING CHANGE(requirements): bump minimum Next.js version to v11

  What: next-pwa's minimum supported Next.js version is now 11.0.0.

  Why: I noticed that workbox-webpack-plugin no longer works with Next.js 9 and 10, so this bumps the minimum supported Next.js version to v11.

  How to upgrade: Bump next to at least 11.0.0.

@ducanh2912/[email protected]

Patch Changes

• #34 9850306 Thanks @DuCanhGH! - fix(next-pwa): fixed __PWA_SW_ENTRY_WORKER__ being undefined

  • This happens when cacheOnFrontEndNav is not enabled, which causes webpack.DefinePlugin to not be called.