Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Sync with react.dev @ 2774ddfa #502

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

Open
react-translations-bot wants to merge 9 commits into main
base: main
Choose a base branch
Loading
from sync-2774ddfa
Open

Conversation

@react-translations-bot
Copy link
Collaborator

@react-translations-bot react-translations-bot commented Sep 1, 2025

This PR was automatically generated.

Merge changes from react.dev at 2774ddf

DO NOT SQUASH MERGE THIS PULL REQUEST!

Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.

crutchcorn and others added 9 commits August 22, 2025 18:13
...nts (#7939)
Co-authored-by: Sebastian "Sebbie" Silbermann <silbermann.sebastian@gmail.com>
Co-authored-by: Aimen Ben Amor <aimen_ben_amor@epam.com>
* Add CityJS New Delhi 2026 conference details
* Update CityJS New Delhi date to 2025
The previous sentence "If you are using React Compiler, useMemo, useCallback, and React.memo can be removed." was coming off a bit too strong and makes it incorrectly seem like the manual memos and compiler memos are 1:1.
Removing the sentence doesn't take anything away from this paragraph, so let's remove it to reduce confusion.
Updates our previous RC blogpost to point people to the `rc` tag, not the specific rc version
The compiler rule is now enabled by default in 6.0.0-rc.2, so there is no longer a need to manually enable the compiler rule in user's eslint configs.
Copy link

vercel bot commented Sep 1, 2025
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
vi-legacy-reactjs-org Ignored Ignored Preview Sep 1, 2025 5:01am

Copy link

github-actions bot commented Sep 1, 2025

Size changes

Details

📦 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.27 KB (🟡 +40 B) 238.75 KB
/500 128.28 KB (🟡 +41 B) 238.76 KB
/[[...markdownPath]] 130.36 KB (🟡 +39 B) 240.85 KB
/errors 128.52 KB (🟡 +40 B) 239 KB
/errors/[errorCode] 128.5 KB (🟡 +40 B) 238.98 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.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /