Skip to content

Conversation

poteto
Copy link
Member

@poteto poteto commented Oct 9, 2025

Updates our blog posts and docs for React Compiler 1.0

Copy link

github-actions bot commented Oct 9, 2025

Size changes

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Five 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 128.11 KB (🟡 +6 B) 238.65 KB
/500 128.12 KB (🟡 +6 B) 238.66 KB
/[[...markdownPath]] 130.56 KB (🟡 +6 B) 241.1 KB
/errors 128.36 KB (🟡 +6 B) 238.9 KB
/errors/[errorCode] 128.34 KB (🟡 +6 B) 238.88 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.

Updates our blog posts and docs for React Compiler 1.0
### React Compiler is now stable! {/*react-compiler-is-now-in-rc*/}

Please see the [RC blog post](/blog/2025/04/21/react-compiler-rc) for details.
Please see the [stable release blog post](/blog/2025/10/08/react-compiler-1) for details.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love that we’re updating our old blog posts to help developers avoid outdated information.

That said it’s really important to not break links, and not rewrite history. So here and in other places, let’s keep the existing text and add an update about the stable release. Strikethrough text for what was there works too, but let’s not rewrite so aggressively.

Copy link
Member

@josephsavona josephsavona left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment, let’s avoid breaking links and rewriting history

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants