@ducanh2912/next-pwa@10.0.2

Patch Changes

• 9107baa Thanks @DuCanhGH! - fix(cofen): fixed type errors

@ducanh2912/next-pwa@10.0.1

Patch Changes

• #127 a4b8926 Thanks @DuCanhGH! - fix(cache-on-front-end-nav): fixed error 'URL object could not be cloned.'

  • This was due to us trying to send the URL object to our worker through postMessage.

@ducanh2912/next-pwa@10.0.0

NOTE: If there's no specific reason to continue using @ducanh2912/next-pwa, consider migrating to @serwist/next. This version (10.0.0) is the LAST PLANNED major version for @ducanh2912/next-pwa. It is now under maintenance mode and will not receive as many feature updates as it used to.

Major Changes

• 52d2390 Thanks @DuCanhGH! - chore(backporting): backported some changes from @serwist/next@8.0.0

  • Removed buildExcludes.
    • Simply use workboxOptions.exclude as a replacement.
  • Removed customWorkerDir.
    • Use customWorkerSrc instead.
  • Removed browserslist, swcMinify, watchWorkersInDev.
    • We now create child compilers on Next.js's compiler instead of starting separate Webpack processes.
    • This also means you don't need to have @swc/core installed anymore.
  • Change the default value for dest from ".next" to "public".
    • You should change it to ".next" in your project if there's demand, but I'd recommend using "public" instead.
  • Fixed the custom worker and the fallback worker not working...
    • This was caused by next-pwa's importScripts not being passed to Workbox. I'm seriously sorry...
  • Moved the minimum supported Next.js version from 11.0.0 to 14.0.0.
    • This is to remove the appDir check.

Patch Changes

• #115 974326e Thanks @vlad-yakovlev! - fix(next-auth): allow users to use the application offline

@ducanh2912/next-pwa@9.7.2

Patch Changes

• 78ce4fb Thanks @DuCanhGH! - fix(next-pwa): fixed InjectManifest crashing due to babelPresetEnvTargets being set

  • I'm still astonished that noone, including me, has noticed this issue all this time 💀. Really unfortunately speaks volumes about how popular this feature is among us, though.
  • This also fixes our applying defaults for GenerateSW, so if there's any unexpected change that arises from this, I'm really sorry. This affects you if you use importScripts, which used to cause the custom worker and the fallback worker to not be imported into your service worker.

@ducanh2912/next-pwa@9.7.1

Patch Changes

• #96 27d5f20 Thanks @DuCanhGH! - fix: remove lazy and importInterop from .swcrc

  • Seems that these values are no longer allowed with module.type set to "es6" or "nodenext".

  • In addition, jsc.parser.tsx has been set to false as it doesn't really make sense to use React in these workers.

@ducanh2912/next-pwa@9.7.0

Minor Changes

• #90 c24e175 Thanks @DuCanhGH! - feat: added watchWorkersInDev

  • Note that this feature is disabled by default, and can be enabled by setting PluginOptions.watchWorkersInDev to true. After a change is detected and webpack rebuilds the custom worker, you have to reload the page for it to take effect.

• #90 c24e175 Thanks @DuCanhGH! - feat: added .webm to defaultCache's static-video-assets

  • I think it'd be nice to support this extension as well, and this shouldn't cause a breaking change (if there is another entry that matches .webm files in workboxOptions.runtimeCaching and extendDefaultRuntimeCaching, then Workbox will still pick that entry).

@ducanh2912/next-pwa@9.6.0

Minor Changes

• #84 12a6542 Thanks @DuCanhGH! - feat: added PluginOptions.browserslist

  • This defaults to "chrome >= 56", same with Workbox's default.
  • Note that .browserslistrc, package.json.browserslist, etc. are not supported (yet), and the only way to pass the config to next-pwa is PluginOptions.browserslist, but you can read the file yourself, parse it, then pass it to next-pwa.
  • This allows you to configure which browsers you want to target your workers for. This tells next-pwa to add PluginOptions.workboxOptions.babelPresetEnvTargets if that option is not defined, which means that the service worker will, too, be bundled to target these browsers, but you can change that by adding the option.

• #84 12a6542 Thanks @DuCanhGH! - feat: support Next's new logging style

  • So Next changed its logging style again, and I'm wondering if trying to match its logging style is even a good idea.

@ducanh2912/next-pwa@9.5.0

Minor Changes

• #74 158ebe1 Thanks @DuCanhGH! - refactor: removed 'activated' event listeners in sw-entry.ts

  • These listeners seem to be unnecessary as we already have runtimeCaching. Though, this is merely an assumption and might cause issues for some people.
    Do open a new issue if you are one of them :)
  • This also updates every dependency to their latest versions.

@ducanh2912/next-pwa@9.4.0

Minor Changes

• #62 771de70 Thanks @DuCanhGH! - feat(next-pwa): added customWorkerDest, customWorkerPrefix, use file hashing for workers' output filenames' suffix

  • customWorkerPrefix works like our sw option, except that it is just a prefix and not the whole name to allow having a hash at the end of the custom worker's output filename.
  • This also deprecates customWorkerDir and replaces it with customWorkerSrc to align with customWorkerDest so as to avoid confusion.
  • We now use file hashing instead of buildId for our workers' output filenames' suffix.

@ducanh2912/next-pwa@9.3.0

Minor Changes

• #58 b88526a Thanks @DuCanhGH! - chore: revert adding webpack to dependencies

  • This version reverts that now that Next 13.4.10 has been released, which fixes the issue in which workbox-webpack-plugin fails to resolve webpack in
    development mode.
  • Note: If you are using Next 13.4.9, you will need to install webpack as a devDependency to avoid the aforementioned issue. This is quite a breaking
    change, but it is due to a bug and I've decided against making a major jump. It is recommended to just upgrade to Next 13.4.10 (and still have webpack installed, as it is one of our peerDependencies).