Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages #365

Merged
merged 1 commit into from
Jul 10, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions .changeset/curvy-boats-promise.md

This file was deleted.

11 changes: 0 additions & 11 deletions .changeset/few-garlics-shout.md

This file was deleted.

7 changes: 0 additions & 7 deletions .changeset/lemon-pears-burn.md

This file was deleted.

20 changes: 0 additions & 20 deletions .changeset/slimy-lemons-taste.md

This file was deleted.

13 changes: 0 additions & 13 deletions .changeset/wicked-radios-yawn.md

This file was deleted.

21 changes: 21 additions & 0 deletions packages/eslint-plugin-next-on-pages/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
2 changes: 1 addition & 1 deletion packages/eslint-plugin-next-on-pages/package.json
Original file line number Diff line number Diff line change
@@ -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",
Expand Down
31 changes: 30 additions & 1 deletion packages/next-on-pages/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down Expand Up @@ -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 };
```
Expand Down
2 changes: 1 addition & 1 deletion packages/next-on-pages/package.json
Original file line number Diff line number Diff line change
@@ -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",
Expand Down