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 main, this PR will be updated.
Releases
[email protected]
Minor Changes
f1f5a95: remove eslint
missing-image-loader
rulethe
missing-image-loader
rule is no longer needed since@cloudflare/next-on-pages
version 1.3.0 as basic support for the
Image
component has been introduced(in the following PR: feat: images support via
/_next/image
#357), therefore there isn'ta real need to warn developers not to use the
Image
component without a custom loader(since the component will just work by default).
@cloudflare/[email protected]
Minor Changes
cb7ab43: Support for images via
/_next/image
, falling back to the raw image URL when image resizing is not available.Due to limitations with Cloudflare Pages, it is not currently possible to send requests through image resizing.
Patch Changes
cf5234a: Prevent the build process from modifying the
.vercel/output/functions
directory.92c865b: deduplicate Next.js manifests
Currently in our functions files we have end up having a number of Next.js internally used manifest objects duplicated.
These manifests increase as the number of routes increases making the size effects of the duplication quite problematic for medium/large applications
(for small applications the manifest duplication is not as problematic).
This change removes such duplication by making sure that we only include each type of manifest once and share such javascript object across the various functions instead (significantly decreasing the output size of medium/large next-on-pages applications).
505be1e: avoid extracting chunks when unnecessary
As part of our lazy loading implementation (see https://github.com/cloudflare/next-on-pages/blob/main/docs/technical/lazy-loading.md)
we extract chunks that are used by different routes into separate functions and import those functions in the route files, this allows
us not to duplicate chunks code.
This change here makes sure that only the chunks that are actually used by multiple routes get extracted as there isn't a real benefit
in extracting into separate files chunks that are used by single routes, on the contrary it actually adds overhead and increases
the number of files produced, which for large next-on-pages applications might be problematic.