Skip to content
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 @ 56df8af5 #673

Merged
merged 52 commits into from
Jun 20, 2024
Merged

Sync with react.dev @ 56df8af5 #673

merged 52 commits into from
Jun 20, 2024

Conversation

react-translations-bot
Copy link
Collaborator

@react-translations-bot react-translations-bot commented Jun 17, 2024

This PR was automatically generated.

Merge changes from react.dev at 56df8af

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.

rickhanlonii and others added 30 commits May 1, 2024 15:23
Thanks to @SAWARATSUKI for updating the logo!
Change the tense of "build" to "building".
* Update synchronizing-with-effects.md

Currently documentation says:

By default, your Effect will run after every render.

Which is in contrast with another section of the same page where it says:

Effects run at the end of a commit after the screen updates

* Update src/content/learn/synchronizing-with-effects.md

---------

Co-authored-by: Ricky <[email protected]>
* Fix #6854: node.js version upgrade

* Fix #6854: node.js version update
* Update team.md: Jason Bonta

* Update src/content/community/team.md

Lauren's suggestion

Co-authored-by: lauren <[email protected]>

---------

Co-authored-by: lauren <[email protected]>
* Add initial skeleton

* Scaffold compiler docs structure

* Braindump for getting started

* Add intro

* tweaks

* add experimental tag

* flesh more out of index page

* flesh out installation

* add installation intro

* update install instrs

* add section on eslint plugin

* reorg

* add incremental guide

* [debugging] Add section about devtools badge

* [debugging] Add section about using logger

* Update next.js instructions

* reporting issues

* [debugging] Add section on useEffect over firing

* [debugging] Add section about conditional hook call

* Latest updates

* Remove ununsed reference pages

* adding extra context for Remix

---------

Co-authored-by: Sathya Gunasekaran <[email protected]>
Co-authored-by: Lauren Tan <[email protected]>
Co-authored-by: Jason Bonta <[email protected]>
Using "off", "warn", "error" has been supported for many years now - I think this helps improve the readability :) 

I completely forgot what rule: 2 meant - had to find it at 

https://eslint.org/docs/latest/use/configure/rules
Removed ; as it's unnecessary in jsx component
Front end nation is covering a full track of React talks including speakers such as:

* Kent C Dodds
* Sara Vieira
* Tejas Kumar
Co-authored-by: OH HYUN KEUN <[email protected]>
rickhanlonii and others added 16 commits May 23, 2024 12:29
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 <[email protected]>
Fix very minor typo
Copy link

vercel bot commented Jun 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
id-react-dev 🔄 Building (Inspect) Visit Preview 💬 Add feedback Jun 20, 2024 9:22am
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
id-legacy-reactjs-org ⬜️ Ignored (Inspect) Visit Preview Jun 20, 2024 9:22am

Copy link

Size changes

📦 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.14 KB (🟡 +29 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 81.81 KB (🟢 -436 B) 185.96 KB
/500 81.81 KB (🟢 -437 B) 185.95 KB
/[[...markdownPath]] 83.7 KB (🟢 -431 B) 187.84 KB
/errors 82.02 KB (🟢 -435 B) 186.17 KB
/errors/[errorCode] 82 KB (🟢 -434 B) 186.14 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.

@resir014 resir014 merged commit 0dc8bde into main Jun 20, 2024
5 checks passed
@resir014 resir014 deleted the sync-56df8af5 branch June 20, 2024 09:32
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.