Publish packages #39
Merged
Publish packages #39
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
github-actions
bot
force-pushed
the
changeset-release/master
branch
from
8cc52d7
to
8457b17
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@ducanh2912/next-pwa@9.0.0
Major Changes
#38
7bd3ba7Thanks @DuCanhGH! - BREAKING CHANGE(next-pwa, next-sw): use next's swc bindings instead of swc/coreWhat: From now on we will try to resolve
next/dist/build/swcinswc-loader(needed to usecacheOnFrontEndNav, custom workers and offline fallbacks). If it can't be resolved, we will fallback to@swc/core(needed to be installed manually).Why: This is to save disk space (we don't need two
@swc/core) and avoid exceeding Vercel's serverless size limit.Why use Next's
next/dist/build/swc: it seems that@next/mdxis also doing the same for theirmdxRust compiler.How to upgrade: Usually you don't need to do anything. But if you see this line when you build your Next app:
Using @swc/core to compile next-pwa's features. Please install it if you haven't., please do as instructed.#38
7bd3ba7Thanks @DuCanhGH! - BREAKING CHANGE(requirements): bump minimum Next.js version to v11What:
next-pwa's minimum supported Next.js version is now 11.0.0.Why: I noticed that
workbox-webpack-pluginno longer works with Next.js 9 and 10, so this bumps the minimum supported Next.js version to v11.How to upgrade: Bump
nextto at least 11.0.0.@ducanh2912/next-sw@1.1.0
Minor Changes
#38
7bd3ba7Thanks @DuCanhGH! - BREAKING CHANGE(next-pwa, next-sw): use next's swc bindings instead of swc/coreWhat: From now on we will try to resolve
next/dist/build/swcinswc-loader(needed to usecacheOnFrontEndNav, custom workers and offline fallbacks). If it can't be resolved, we will fallback to@swc/core(needed to be installed manually).Why: This is to save disk space (we don't need two
@swc/core) and avoid exceeding Vercel's serverless size limit.Why use Next's
next/dist/build/swc: it seems that@next/mdxis also doing the same for theirmdxRust compiler.How to upgrade: Usually you don't need to do anything. But if you see this line when you build your Next app:
Using @swc/core to compile next-pwa's features. Please install it if you haven't., please do as instructed.