Sync with react.dev @ c3bc5aff #424
Conversation
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
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: ef32fc723722eb5119529abcc572dd2bcf2b1cab 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe 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 If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! Five Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly 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 Any third party scripts you have added directly to your app using the 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 c3bc5af
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.