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 @ 9967ded3 #423

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Conversation

react-translations-bot
Copy link
Collaborator

This PR was automatically generated.

Merge changes from react.dev at 9967ded

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.

includerajat and others added 13 commits May 13, 2024 13:47
Co-authored-by: Rajat Jindal <rajat@testing.com>
* Update team.md: Jason Bonta

* Update src/content/community/team.md

Lauren's suggestion

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

---------

Co-authored-by: lauren <poteto@users.noreply.github.com>
* 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 <gsathya.ceg@gmail.com>
Co-authored-by: Lauren Tan <poteto@users.noreply.github.com>
Co-authored-by: Jason Bonta <jbonta@gmail.com>
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
Copy link

vercel bot commented May 20, 2024

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

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
vi-legacy-reactjs-org ⬜️ Ignored (Inspect) Visit Preview May 20, 2024 5:01am

Copy link

Size changes

📦 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 81.29 KB (🟡 +18 B) 185.44 KB
/500 81.29 KB (🟡 +18 B) 185.44 KB
/[[...markdownPath]] 83.13 KB (🟡 +18 B) 187.28 KB
/errors 81.5 KB (🟡 +18 B) 185.65 KB
/errors/[errorCode] 81.48 KB (🟡 +18 B) 185.63 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.