Skip to content

Sync with react.dev @ 6274d4fa#57

Open
react-translations-bot wants to merge 37 commits intomainfrom
sync-6274d4fa
Open

Sync with react.dev @ 6274d4fa#57
react-translations-bot wants to merge 37 commits intomainfrom
sync-6274d4fa

Conversation

@react-translations-bot
Copy link
Copy Markdown
Collaborator

This PR was automatically generated.

Merge changes from react.dev at 6274d4f

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.

rickhanlonii and others added 30 commits May 20, 2024 10:53
Co-authored-by: OH HYUN KEUN <ohhk@uitgis.com>
This upstreams some of the [introduction
post](reactwg/react-compiler#5) into the
docs since this knowledge is quite fundamental to understanding the
compiler, and it's confusing to not have it linked in the canonical
source for the docs. It also adds more information about
[debugging](reactwg/react-compiler#7) and
reorganizes a few sections to make things clearer

ghstack-source-id: ef32fc7
Pull Request resolved: reactjs/react.dev#6895
* Add React Conf 2024 Recap post

* Spelling and links

* Apply suggestions from code review

Co-authored-by: lauren <poteto@users.noreply.github.com>

* Edits

* Edits

* better link

* Update date

* Update date and nits

* feedback

---------

Co-authored-by: lauren <poteto@users.noreply.github.com>
* Add codemods to upgrade guide

* Update src/content/blog/2024/04/25/react-19-upgrade-guide.md

Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com>

* Add benefits

---------

Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com>
The docs for stylesheet precedence incorrectly state that there is an enumerated set of valid precedences. This is incorrect. The precedence value can be anything and React infers the hierarchy from the order in which it discovers precedences
* FIX: Typo in useEffect.md caveats

* Fix another typo
* Add act documentation

* Update structure based on feedback

* Add usage examples and async act

---------

Co-authored-by: Rick Hanlon <rickhanlonii@fb.com>
Fix very minor typo
Added missing comma to the codesample.
Expo now has its own instructions for enabling the compiler.
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 22, 2024

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

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

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 104.19 KB (🟡 +44 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 104.28 KB (🔴 +23.16 KB) 208.47 KB
/500 104.27 KB (🔴 +23.16 KB) 208.46 KB
/[[...markdownPath]] 106.12 KB (🔴 +23.16 KB) 210.31 KB
/errors 104.48 KB (🔴 +23.16 KB) 208.68 KB
/errors/[errorCode] 104.46 KB (🔴 +23.16 KB) 208.66 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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.