-
Notifications
You must be signed in to change notification settings - Fork 10
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
Sync with react.dev @ b22cbc3f #78
base: main
Are you sure you want to change the base?
Conversation
* fix links * Update startTransition.md * Update startTransition.md * Update startTransition.md * Update startTransition.md
"use-server" docs Server Functions href fixed.
* Fix stylesheet precedence example * Update link.md --------- Co-authored-by: dan <dan.abramov@gmail.com>
Co-authored-by: Josue Navas <josue.navas@eagleview.com>
docs: fixed typo act md counter fn grammar error
… appropriate section (#7354)
the “Dealing with rejected Promises” codesandbox example depends on react-error-boundary, but doesn’t specify it as a dependency, so the code example is broken
… React Native (#7369) * docs[compiler]: clarify React DevTools support for Compiler Badges in React Native * Update react-compiler.md * Update react-compiler.md --------- Co-authored-by: dan <dan.abramov@gmail.com>
* fix: remove forwardref from useImperativeHandle docs * Make changes more focused * Update useImperativeHandle.md --------- Co-authored-by: dan <dan.abramov@gmail.com>
* App.js 2025 * reorder
…umentation for clarity (#7377)
…h Refs pages (#7364)
In the section "Importing Server Functions from Client Components" updated "createNoteAction" to "createNote" to match the function name in the example
Added React Universe Conf 2025 to the list of conferences
Co-authored-by: Sebastian Markbåge <sebastian@calyptus.eu> Co-authored-by: Rick Hanlon <rickhanlonii@fb.com> Co-authored-by: eps1lon <sebastian.silbermann@vercel.com>
* Update Conferences Lists for 2025 * fix typo * Fix typo
…blog posts (#7431)
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
110.38 KB (🟡 +6 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 |
125.07 KB (🔴 +19.12 KB) |
235.45 KB |
/500 |
125.08 KB (🔴 +19.13 KB) |
235.46 KB |
/[[...markdownPath]] |
126.94 KB (🔴 +19.2 KB) |
237.32 KB |
/_error |
190 B (🟡 +9 B) |
110.57 KB |
/errors |
125.35 KB (🔴 +19.19 KB) |
235.73 KB |
/errors/[errorCode] |
125.33 KB (🔴 +19.18 KB) |
235.71 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.
This PR was automatically generated.
Merge changes from react.dev at b22cbc3
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.