Skip to content

CHANGELOG.md

Latest commit

 

History

History
88 lines (55 loc) · 5.08 KB

CHANGELOG.md

File metadata and controls

88 lines (55 loc) · 5.08 KB

@ducanh2912/next-pwa

10.2.3

Patch Changes

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

    • A fast backport of serwist/serwist#56.
    • This is caused by "/_next/../public" in modifyURLPrefix not being matched when basePath is set, since the URL is 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!

10.2.2

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.

10.2.1

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

10.2.0

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.

10.1.0

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.

10.0.2

Patch Changes

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.

10.0.0

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...
      • I'm seriously sorry... This was caused by next-pwa's importScripts not being passed to Workbox.
    • Moved the minimum supported Next.js version from 11.0.0 to 14.0.0.
      • This is to remove the appDir check.

Patch Changes