@ducanh2912/next-pwa@10.2.0
·
38 commits
to master
since this release
Minor Changes
-
f65e6abThanks @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-pwateam for this approach! Learned a lot through forkingvite-plugin-pwa, that's for sure.
- I'd like to extend my thanks to the
- 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-pwahas been fixed. If you don't provideadditionalManifestEntries,@ducanh2912/next-pwanow runsfast-globon your public folder for you. The oldnext-pwa, too, did this, but an extra?? []in our fork ruined that...
- We now leverage a context to share the user's options for Webpack, Next.js,