From f3fa7fe5d3ee1bfa98bf53720c99108e32abb3af Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Mon, 10 Jul 2023 16:06:47 +0000 Subject: [PATCH] Version Packages --- .changeset/curvy-boats-promise.md | 5 --- .changeset/few-garlics-shout.md | 11 ------- .changeset/lemon-pears-burn.md | 7 ----- .changeset/slimy-lemons-taste.md | 20 ------------ .changeset/wicked-radios-yawn.md | 13 -------- .../eslint-plugin-next-on-pages/CHANGELOG.md | 21 +++++++++++++ .../eslint-plugin-next-on-pages/package.json | 2 +- packages/next-on-pages/CHANGELOG.md | 31 ++++++++++++++++++- packages/next-on-pages/package.json | 2 +- 9 files changed, 53 insertions(+), 59 deletions(-) delete mode 100644 .changeset/curvy-boats-promise.md delete mode 100644 .changeset/few-garlics-shout.md delete mode 100644 .changeset/lemon-pears-burn.md delete mode 100644 .changeset/slimy-lemons-taste.md delete mode 100644 .changeset/wicked-radios-yawn.md diff --git a/.changeset/curvy-boats-promise.md b/.changeset/curvy-boats-promise.md deleted file mode 100644 index bb3b9ff04..000000000 --- a/.changeset/curvy-boats-promise.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@cloudflare/next-on-pages': patch ---- - -Prevent the build process from modifying the `.vercel/output/functions` directory. diff --git a/.changeset/few-garlics-shout.md b/.changeset/few-garlics-shout.md deleted file mode 100644 index 8870394f3..000000000 --- a/.changeset/few-garlics-shout.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -'@cloudflare/next-on-pages': patch ---- - -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). diff --git a/.changeset/lemon-pears-burn.md b/.changeset/lemon-pears-burn.md deleted file mode 100644 index 5c2370e50..000000000 --- a/.changeset/lemon-pears-burn.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@cloudflare/next-on-pages': minor ---- - -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. diff --git a/.changeset/slimy-lemons-taste.md b/.changeset/slimy-lemons-taste.md deleted file mode 100644 index e965037b9..000000000 --- a/.changeset/slimy-lemons-taste.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -'eslint-plugin-next-on-pages': minor ---- - -remove eslint `missing-image-loader` rule - -the `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: https://github.com/cloudflare/next-on-pages/pull/357), therefore there isn't -a real need to warn developers not to use the `Image` component without a custom loader -(since the component will just work by default). - -> **Warning** -> This is technically a breaking change to the `eslint-plugin-next-on-pages` package -> since linting would break for users specifically including the `missing-image-loader` -> rule (causing `Definition for rule 'next-on-pages/missing-loader' was not found` errors) -> however currently we don't assume that many people are using the plugin with the rule -> specifically included, moreover the resolution for the breaking change is to simply -> remove the rule from the application's eslint configuration so it is also extremely -> simple to fix, thus we didn't consider this worth a major bump diff --git a/.changeset/wicked-radios-yawn.md b/.changeset/wicked-radios-yawn.md deleted file mode 100644 index 1c4c78a25..000000000 --- a/.changeset/wicked-radios-yawn.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -'@cloudflare/next-on-pages': patch ---- - -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. diff --git a/packages/eslint-plugin-next-on-pages/CHANGELOG.md b/packages/eslint-plugin-next-on-pages/CHANGELOG.md index 5e0199c35..6ee25a2b7 100644 --- a/packages/eslint-plugin-next-on-pages/CHANGELOG.md +++ b/packages/eslint-plugin-next-on-pages/CHANGELOG.md @@ -1,5 +1,26 @@ # eslint-plugin-next-on-pages +## 1.3.0 + +### Minor Changes + +- f1f5a95: remove eslint `missing-image-loader` rule + + the `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: https://github.com/cloudflare/next-on-pages/pull/357), therefore there isn't + a real need to warn developers not to use the `Image` component without a custom loader + (since the component will just work by default). + + > **Warning** + > This is technically a breaking change to the `eslint-plugin-next-on-pages` package + > since linting would break for users specifically including the `missing-image-loader` + > rule (causing `Definition for rule 'next-on-pages/missing-loader' was not found` errors) + > however currently we don't assume that many people are using the plugin with the rule + > specifically included, moreover the resolution for the breaking change is to simply + > remove the rule from the application's eslint configuration so it is also extremely + > simple to fix, thus we didn't consider this worth a major bump + ## 1.2.0 ### Patch Changes diff --git a/packages/eslint-plugin-next-on-pages/package.json b/packages/eslint-plugin-next-on-pages/package.json index 09c347d1f..c9e68b266 100644 --- a/packages/eslint-plugin-next-on-pages/package.json +++ b/packages/eslint-plugin-next-on-pages/package.json @@ -1,6 +1,6 @@ { "name": "eslint-plugin-next-on-pages", - "version": "1.2.0", + "version": "1.3.0", "main": "dist/index.js", "scripts": { "prebuild": "rimraf dist", diff --git a/packages/next-on-pages/CHANGELOG.md b/packages/next-on-pages/CHANGELOG.md index 4afed06db..ce0681159 100644 --- a/packages/next-on-pages/CHANGELOG.md +++ b/packages/next-on-pages/CHANGELOG.md @@ -1,5 +1,34 @@ # @cloudflare/next-on-pages +## 1.3.0 + +### 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. + ## 1.2.0 ### Minor Changes @@ -98,7 +127,7 @@ // file: .vercel/output/static/_worker.js/__next-on-pages-dist__/chunks/649.js import wasm_fbeb8adedbc833032bda6f13925ba235b8d09114 from '../wasm/wasm_fbeb8adedbc833032bda6f13925ba235b8d09114.wasm'; var a = b => { - b.exports = wasm_fbeb8adedbc833032bda6f13925ba235b8d09114; + b.exports = wasm_fbeb8adedbc833032bda6f13925ba235b8d09114; }; export { a as default }; ``` diff --git a/packages/next-on-pages/package.json b/packages/next-on-pages/package.json index 0025d2d5c..dba140a4f 100644 --- a/packages/next-on-pages/package.json +++ b/packages/next-on-pages/package.json @@ -1,6 +1,6 @@ { "name": "@cloudflare/next-on-pages", - "version": "1.2.0", + "version": "1.3.0", "bin": "./bin/index.js", "scripts": { "lint": "eslint src",