fix(deps): update dependency @ducanh2912/next-pwa to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@ducanh2912/next-pwa (source)	^9.4.0 -> ^10.0.0

---

Release Notes

DuCanhGH/next-pwa (@​ducanh2912/next-pwa)

v10.2.9

Compare Source

Patch Changes

• f3766a5 Thanks @​DuCanhGH! - chore(deps): updated all dependencies

  • Monthly dependencies maintenance

  • Not so monthly this time...

v10.2.8

Compare Source

Patch Changes

• d43ba6c Thanks @​DuCanhGH! - chore(deps): monthly dependencies maintenance

v10.2.7

Compare Source

Patch Changes

• a1f09b3 Thanks @​DuCanhGH! - chore(next-pwa): removed clean-webpack-plugin

  • This plugin is... unmaintained, and we could use fs.rmSync anyway.

v10.2.6

Compare Source

v10.2.5

Compare Source

Patch Changes

• e6ce949 Thanks @​DuCanhGH! - fix(core): fixed using fallbacks with files in the public directory

  • Silly mistakes... Sorry for the inconvenience.

v10.2.4

Compare Source

Patch Changes

• 07c8861 Thanks @​DuCanhGH! - fix(core): fixed invalid precache manifest with assetPrefix

  • Turns out it is much more complex than we thought. To make this work with assetPrefix, distDir, and basePath, we now remove ${publicPath}${publicDirRelativeToOutputPath} from public files in manifestTransforms because assetPrefix is not intended for files that are in the public directory and we also want to remove /_next/${publicDirRelativeToOutputPath} from the URL, since that is not how we resolve files in the public directory.

v10.2.3

Compare Source

Patch Changes

• e5f1d14 Thanks @​DuCanhGH! - fix(core): fixed invalid precache manifest and scope with basePath

  • A fast backport of serwist/serwist#56.
  • This was caused by "/_next/../public" in modifyURLPrefix not being matched when basePath was set, since the URL was actually "${basePath}/_next/../public/**/*". We now use manifestTransforms instead of modifyURLPrefix.
  • Also, with the refactor to using a context, we mistakenly changed scope from "${scope}" (suffixed with / if originally not) to "${basePath}/${scope}". This reverts that change. Sorry for the inconvenience!

v10.2.2

Compare Source

Patch Changes

• e583be6 Thanks @​DuCanhGH! - fix(disable): fixed disable not working properly

  • In 10.2.0 and 10.2.1, when disable was set, certain unexpected parts were still processed, causing the resulting app to contain some erroneous JavaScript.
  • This has been fixed in 10.2.2. Although we still run parseOptions, we only do so to get the default options.

v10.2.1

Compare Source

Patch Changes

• aeb0dc9 Thanks @​DuCanhGH! - fix(mjs): fixed the ESM build crashing

  • This was due to us referencing __dirname, which was undefined in the ESM build...

v10.2.0

Compare Source

Minor Changes

• f65e6ab Thanks @​DuCanhGH! - refactor(core): create a context

  • We now leverage a context to share the user's options for Webpack, Next.js, next-pwa, TypeScript, etc. across the codebase. This is better than the old approach, which was similar to props drilling, in that it is more readable and less error-prone.
    • I'd like to extend my thanks to the vite-pwa team for this approach! Learned a lot through forking vite-plugin-pwa, that's for sure.
  • Additionally, the codebase now leverages Biome.js instead of Prettier and ESLint. For now, pre-commit hooks using Husky are not available.
  • Edit: Also, an age-old bug in @ducanh2912/next-pwa has been fixed. If you don't provide additionalManifestEntries, @ducanh2912/next-pwa now runs fast-glob on your public folder for you. The old next-pwa, too, did this, but an extra ?? [] in our fork ruined that...

v10.1.0

Compare Source

Minor Changes

• #​130 9ff6c29 Thanks @​DuCanhGH! - feat(next-pwa): re-adjust workboxOptions.exclude defaults

  • This was long overdue, so here we are.
  • Why?
    • This proves to be more sensible than the old defaults.
  • Would this incur a breaking change?
    • Technically yes according to my definitions of a breaking change. It will cause a behavioural change in the built app, unexpectedly so for those who don't pinpoint their dependencies' versions. However, I don't believe this has an impact big enough. This... simply improves the user experience, and it won't cause any build to suddenly fail.

v10.0.2

Compare Source

Patch Changes

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

v10.0.1

Compare Source

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.

v10.0.0

Compare Source

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/[email protected]

  • 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

v9.7.2

Compare Source

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.

v9.7.1

Compare Source

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.

v9.7.0

Compare Source

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).

v9.6.0

Compare Source

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.

v9.5.0

Compare Source

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.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
noisekun	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 27, 2024 3:09pm