fix(deps): update dependency @ducanh2912/next-pwa to v10 #636
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
deps/ducanh2912-next-pwa-10.x
branch
from
9fdff1e
to
a1c6aab
Compare
| datasource | package | from | to | | ---------- | -------------------- | ----- | ------ | | npm | @ducanh2912/next-pwa | 9.4.0 | 10.1.0 |
renovate
bot
force-pushed
the
deps/ducanh2912-next-pwa-10.x
branch
from
a1c6aab
to
d9961c8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.0Release Notes
DuCanhGH/next-pwa (@ducanh2912/next-pwa)
v10.2.7Compare Source
Patch Changes
a1f09b3Thanks @DuCanhGH! - chore(next-pwa): removedclean-webpack-pluginfs.rmSyncanyway.v10.2.6Compare Source
v10.2.5Compare Source
Patch Changes
e6ce949Thanks @DuCanhGH! - fix(core): fixed using fallbacks with files in the public directoryv10.2.4Compare Source
Patch Changes
07c8861Thanks @DuCanhGH! - fix(core): fixed invalid precache manifest withassetPrefixassetPrefix,distDir, andbasePath, we now remove${publicPath}${publicDirRelativeToOutputPath}from public files inmanifestTransformsbecauseassetPrefixis 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.3Compare Source
Patch Changes
e5f1d14Thanks @DuCanhGH! - fix(core): fixed invalid precache manifest and scope withbasePathmanifestTransformsinstead ofmodifyURLPrefix.scopefrom "${scope}" (suffixed with / if originally not) to "${basePath}/${scope}". This reverts that change. Sorry for the inconvenience!v10.2.2Compare Source
Patch Changes
e583be6Thanks @DuCanhGH! - fix(disable): fixeddisablenot working properlydisablewas 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.1Compare Source
Patch Changes
aeb0dc9Thanks @DuCanhGH! - fix(mjs): fixed the ESM build crashing__dirname, which wasundefinedin the ESM build...v10.2.0Compare Source
Minor Changes
f65e6abThanks @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-pwateam for this approach! Learned a lot through forkingvite-plugin-pwa, that's for sure.@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...v10.1.0Compare Source
Minor Changes
#130
9ff6c29Thanks @DuCanhGH! - feat(next-pwa): re-adjustworkboxOptions.excludedefaultsv10.0.2Compare Source
Patch Changes
9107baaThanks @DuCanhGH! - fix(cofen): fixed type errorsv10.0.1Compare Source
Patch Changes
#127
a4b8926Thanks @DuCanhGH! - fix(cache-on-front-end-nav): fixed error 'URL object could not be cloned.'postMessage.v10.0.0Compare 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
52d2390Thanks @DuCanhGH! - chore(backporting): backported some changes from@serwist/next@8.0.0buildExcludes.workboxOptions.excludeas a replacement.customWorkerDir.customWorkerSrcinstead.browserslist,swcMinify,watchWorkersInDev.@swc/coreinstalled anymore.destfrom".next"to"public".".next"in your project if there's demand, but I'd recommend using"public"instead.next-pwa'simportScriptsnot being passed to Workbox. I'm seriously sorry...Patch Changes
974326eThanks @vlad-yakovlev! - fix(next-auth): allow users to use the application offlinev9.7.2Compare Source
Patch Changes
78ce4fbThanks @DuCanhGH! - fix(next-pwa): fixed InjectManifest crashing due tobabelPresetEnvTargetsbeing 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.1Compare Source
Patch Changes
#96
27d5f20Thanks @DuCanhGH! - fix: removelazyandimportInteropfrom.swcrcSeems that these values are no longer allowed with
module.typeset to"es6"or"nodenext".In addition,
jsc.parser.tsxhas been set to false as it doesn't really make sense to use React in these workers.v9.7.0Compare Source
Minor Changes
#90
c24e175Thanks @DuCanhGH! - feat: addedwatchWorkersInDevPluginOptions.watchWorkersInDevtotrue. After a change is detected andwebpackrebuilds the custom worker, you have to reload the page for it to take effect.#90
c24e175Thanks @DuCanhGH! - feat: added.webmtodefaultCache'sstatic-video-assets.webmfiles inworkboxOptions.runtimeCachingandextendDefaultRuntimeCaching, then Workbox will still pick that entry).v9.6.0Compare Source
Minor Changes
#84
12a6542Thanks @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-pwaisPluginOptions.browserslist, but you can read the file yourself, parse it, then pass it tonext-pwa.next-pwato addPluginOptions.workboxOptions.babelPresetEnvTargetsif 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
12a6542Thanks @DuCanhGH! - feat: support Next's new logging stylev9.5.0Compare Source
Minor Changes
#74
158ebe1Thanks @DuCanhGH! - refactor: removed'activated'event listeners insw-entry.tsruntimeCaching. 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 has been generated by Mend Renovate. View repository job log here.