fix(deps): update dependency @ducanh2912/next-pwa to v10 #636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^9.4.0
->^10.0.0
Release Notes
DuCanhGH/next-pwa (@ducanh2912/next-pwa)
v10.2.8
Compare Source
Patch Changes
d43ba6c
Thanks @DuCanhGH! - chore(deps): monthly dependencies maintenancev10.2.7
Compare Source
Patch Changes
a1f09b3
Thanks @DuCanhGH! - chore(next-pwa): removedclean-webpack-plugin
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 directoryv10.2.4
Compare Source
Patch Changes
07c8861
Thanks @DuCanhGH! - fix(core): fixed invalid precache manifest withassetPrefix
assetPrefix
,distDir
, andbasePath
, we now remove${publicPath}${publicDirRelativeToOutputPath}
from public files inmanifestTransforms
becauseassetPrefix
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 withbasePath
manifestTransforms
instead ofmodifyURLPrefix
.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): fixeddisable
not working properlydisable
was set, certain unexpected parts were still processed, causing the resulting app to contain some erroneous JavaScript.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__dirname
, which wasundefined
in the ESM build...v10.2.0
Compare Source
Minor Changes
f65e6ab
Thanks @DuCanhGH! - refactor(core): create a contextnext-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.vite-pwa
team for this approach! Learned a lot through forkingvite-plugin-pwa
, that's for sure.@ducanh2912/next-pwa
has been fixed. If you don't provideadditionalManifestEntries
,@ducanh2912/next-pwa
now runsfast-glob
on your public folder for you. The oldnext-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-adjustworkboxOptions.exclude
defaultsv10.0.2
Compare Source
Patch Changes
9107baa
Thanks @DuCanhGH! - fix(cofen): fixed type errorsv10.0.1
Compare Source
Patch Changes
#127
a4b8926
Thanks @DuCanhGH! - fix(cache-on-front-end-nav): fixed error 'URL object could not be cloned.'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]
buildExcludes
.workboxOptions.exclude
as a replacement.customWorkerDir
.customWorkerSrc
instead.browserslist
,swcMinify
,watchWorkersInDev
.@swc/core
installed anymore.dest
from".next"
to"public"
.".next"
in your project if there's demand, but I'd recommend using"public"
instead.next-pwa
'simportScripts
not being passed to Workbox. I'm seriously sorry...Patch Changes
974326e
Thanks @vlad-yakovlev! - fix(next-auth): allow users to use the application offlinev9.7.2
Compare Source
Patch Changes
78ce4fb
Thanks @DuCanhGH! - fix(next-pwa): fixed InjectManifest crashing due tobabelPresetEnvTargets
being setGenerateSW
, so if there's any unexpected change that arises from this, I'm really sorry. This affects you if you useimportScripts
, 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: removelazy
andimportInterop
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: addedwatchWorkersInDev
PluginOptions.watchWorkersInDev
totrue
. After a change is detected andwebpack
rebuilds the custom worker, you have to reload the page for it to take effect.#90
c24e175
Thanks @DuCanhGH! - feat: added.webm
todefaultCache
'sstatic-video-assets
.webm
files inworkboxOptions.runtimeCaching
andextendDefaultRuntimeCaching
, then Workbox will still pick that entry).v9.6.0
Compare Source
Minor Changes
#84
12a6542
Thanks @DuCanhGH! - feat: addedPluginOptions.browserslist
"chrome >= 56"
, same with Workbox's default..browserslistrc
,package.json.browserslist
, etc. are not supported (yet), and the only way to pass the config tonext-pwa
isPluginOptions.browserslist
, but you can read the file yourself, parse it, then pass it tonext-pwa
.next-pwa
to addPluginOptions.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 stylev9.5.0
Compare Source
Minor Changes
#74
158ebe1
Thanks @DuCanhGH! - refactor: removed'activated'
event listeners insw-entry.ts
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 :)
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.
This PR was generated by Mend Renovate. View the repository job log.