-
Notifications
You must be signed in to change notification settings - Fork 163
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 @ 2b2d0f23 #669
Conversation
Co-authored-by: Sebastian Silbermann <[email protected]>
…(#7108) * Emphasize the second problem acapit with chain of effects example * Replace 'One' with 'First' to keep problems counting consistent
PR to add Radv 2024 conference
Co-authored-by: Tom Eastman <[email protected]>
* Update conferences.md, add conference * Update conferences.md --------- Co-authored-by: Eli White <[email protected]>
…… (#6691) * Changed the documentation of the subscribe argument to a more accurate one. * Update useSyncExternalStore.md --------- Co-authored-by: Sophie Alpert <[email protected]>
reactjsday 2024 React conference in Verona, Italy
* Fix typos in thinking-in-react.md * Update src/content/learn/thinking-in-react.md --------- Co-authored-by: Ricky <[email protected]>
* docs(act.md): correct ReactDOMClient to ReactDOM * docs(act.md): switch the import to ReactDOMClient instead
Co-authored-by: san.s <[email protected]>
…s in sample code (#7126)
* fix: `@testing-library/react-native` links * Apply suggestions from code review --------- Co-authored-by: Ricky <[email protected]>
For users of React < 19, there is a new react-compiler-runtime package that can be used to provide a "polyfill" for runtime APIs needed for compiled code. This PR adds docs for that.
Co-authored-by: Sebastian "Sebbie" Silbermann <[email protected]>
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
104.3 KB (🟡 +536 B) |
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!
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 |
105.43 KB (🟡 +53 B) |
209.73 KB |
/500 |
105.42 KB (🟡 +53 B) |
209.73 KB |
/[[...markdownPath]] |
107.4 KB (🟡 +53 B) |
211.71 KB |
/errors |
105.66 KB (🟡 +53 B) |
209.97 KB |
/errors/[errorCode] |
105.64 KB (🟡 +53 B) |
209.94 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 2b2d0f2
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
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.