Sync with react.dev @ 943e3ce4 #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g conferences (#6246) * update conferences to move react rally to previous and add reactjs day * Add React Alicante * Update conferences.md * Update conferences.md to include year of the event * add anchor link * Update conferences.md * Update conferences.md * chore: update country name --------- Co-authored-by: Strek <[email protected]>
Grammar fix
Added RenderATL 2024 to the conferences Markdown page
Update Twitter(X) icon for light and dark mode
While reading the new typescript docs introduced in #6120, I noticed this link points to a fork. This commit changes it to a relative link so it should work everywhere.
Fix incorrect link in select.md
Co-authored-by: Ricky <[email protected]> Co-authored-by: Luna Wei <[email protected]> Co-authored-by: Ricky Hanlon <[email protected]>
React.lazy dots into the `default` property. Document this.
* [WIP] Add use hook API reference page * [WIP] Update use hook API reference page based on feedback * [WIP] use hook API ref doc: add browser API example * [WIP] use hook API ref doc: add context, lib examples * [WIP] use reference doc - incorporate all current feedback * [WIP] use reference page fix typos * use reference doc: address PR feedback from Luna, Sophia,Eli, and Lee * Apply @harish-sethuraman's typo fixes from code review Co-authored-by: Strek <[email protected]> * use reference doc typo fixes * use reference doc: update style to match other react.dev conventions * minor fixes * Remove client Promises, use canary labels * Add use hook section to index, remove RSC section on components page * Final edits * Clarify use reference caveats --------- Co-authored-by: Strek <[email protected]>
* Update 17 files * remove: legacy react devtool * Update 3 files * fix(editor): allow horizontal scroll * Update SandpackRoot.tsx
corrected links
…llback doesn't seem to be accurate. (#6207) * Update useEffect.md * Update src/content/reference/react/useEffect.md --------- Co-authored-by: Sophie Alpert <[email protected]>
* delete unused useState import * add word to equalize challenge and solutions texts * Refactor some texts * Apply suggestions from code review --------- Co-authored-by: Sophie Alpert <[email protected]>
* Remove pitfall and update Next link * Fix other beta link --------- Co-authored-by: Luna Wei <[email protected]>
* Add useOptimistic API reference documentation * Fix title * Add working exmaple from form and updadd parameters * Add updates to useOptimistic * Add updates to useOptimistic * Add updates to useOptimistic --------- Co-authored-by: Matt Carroll <[email protected]>
Google uses this on many of our API doc pages and it's not a good snippet. Only put this on the homepage but leave the og:description and twitter:description.
* Adds landing page for reference section.) * Updated hyperlinks. * Fixes Legacy APIs link. * Removes canary image from heading.
Co-authored-by: Sophie Alpert <[email protected]> Co-authored-by: Luna Wei <[email protected]>
Co-authored-by: Soichiro Miki <[email protected]> Co-authored-by: David McCabe <[email protected]> Co-authored-by: Luna Wei <[email protected]>
* Edits for new "use client" content * Apply suggestions from code review Co-authored-by: Luna <[email protected]> --------- Co-authored-by: Luna <[email protected]>
Summary of changes: "Server Action", like "Effect", is a React-specific notion that would be benefited from captailization to be distinguished from its genertic meaning. It seems like [Next doc](https://nextjs.org/docs/app/api-reference/functions/server-actions) has also adopted such connventions and we should probably do the same. Co-authored-by: xuan.huang <[email protected]>
Summary of changes: following <reactjs/react.dev#6417> Co-authored-by: xuan.huang <[email protected]>
Summary of changes: See <reactjs/react.dev#6417> Co-authored-by: xuan.huang <[email protected]>
Co-authored-by: Luna Wei <[email protected]>
Summary of changes: See <reactjs/react.dev#6417>. There is one exception though. The error message “Rendered fewer hooks than expected” from React is indeed "hooks" so I kept as-is. Shall we change the error message from React? Co-authored-by: xuan.huang <[email protected]>
Summary of changes: See <reactjs/react.dev#6417> Co-authored-by: xuan.huang <[email protected]>
Summary of changes: See <reactjs/react.dev#6417> Co-authored-by: xuan.huang <[email protected]>
…(#6445) * Fix: component not returned * Fix: missing function statement
Summary of changes: There is one "TypeScript strict mode" that is kept unchanged. Co-authored-by: xuan.huang <[email protected]>
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! Four 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated.
Merge changes from react.dev at 943e3ce
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.