Upgrade to Next 15 Canary and enable React Compiler #6996
Conversation
…pgrade to 15, then enable the complier
…mports are broken
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
107.85 KB (🟡 +3.66 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Six Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load |
|---|---|---|
/404 |
123.38 KB (🔴 +19.11 KB) |
231.24 KB |
/500 |
123.4 KB (🔴 +19.13 KB) |
231.25 KB |
/[[...markdownPath]] |
125.31 KB (🔴 +19.19 KB) |
233.17 KB |
/_error |
189 B (🟡 +8 B) |
108.04 KB |
/errors |
123.67 KB (🔴 +19.19 KB) |
231.52 KB |
/errors/[errorCode] |
123.65 KB (🔴 +19.18 KB) |
231.5 KB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
Co-authored-by: Sebastian Markbåge <[email protected]>
mattcarrollcode
changed the title
mattcarrollcode
changed the title
There was a problem hiding this comment.
@gaearon Do you know if there a better way to do this now? In your PR where you introduced this patch you mentioned that you'd hope there would be a way to customize this back in Next v12.
There was a problem hiding this comment.
this just seemed like maybe a bug? try getting the build to fail in the same way as the PR mentioned in the original PR and see if it passes CI
This change upgrades React.dev from Next 13.4.1 to Next 15 Canary and and enables the React Complier
Preview, 19 Preview