-
Notifications
You must be signed in to change notification settings - Fork 185
Sync with react.dev @ f8c81a0f #871
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
Conversation
Co-authored-by: Fre <[email protected]>
* Updates to Activity docs * wip * Updates to Activity docs: - New intro at top of Reference - Adds "Deferring hydration of low-priority content" section - Move "Preventing hidden content from having unwanted side effects" section to Troubleshooting - Removes SSR section from Troubleshooting * useLayoutEffect + Tidying up * Use the same color code step for "visible" * Tidy * Typo * Update section on selective hydration * Update title * Clean up props * Tweak wording * wip * wip * wip * remove temporary scroll restoration while working on docs * wip * wip
…nts (#7939) Co-authored-by: Sebastian "Sebbie" Silbermann <[email protected]>
Co-authored-by: Aimen Ben Amor <[email protected]>
* Add CityJS New Delhi 2026 conference details * Update CityJS New Delhi date to 2025
The previous sentence "If you are using React Compiler, useMemo, useCallback, and React.memo can be removed." was coming off a bit too strong and makes it incorrectly seem like the manual memos and compiler memos are 1:1. Removing the sentence doesn't take anything away from this paragraph, so let's remove it to reduce confusion.
Updates our previous RC blogpost to point people to the `rc` tag, not the specific rc version
The compiler rule is now enabled by default in 6.0.0-rc.2, so there is no longer a need to manually enable the compiler rule in user's eslint configs.
Co-authored-by: unknown <[email protected]~>
`a expensive` should be `an expensive`
Fix "documentatino" typo to "documentation" in comment about useOptimistic reference page.
…d example of the use API (#7767) * Update "Deep Dive" in reusing-logic-with-custom-hooks.md with link to and example of the use API * Remove mention of Server Components when explaining the use API * Update src/content/learn/reusing-logic-with-custom-hooks.md Co-authored-by: Ricky <[email protected]> * fix: Correct which lines are highlighted in code example --------- Co-authored-by: Ricky <[email protected]>
The previous examples used a service called loremflickr.com to link to placeholder images. Since that service is now down, I updated them to reference placecats.com instead, which we already use in other examples as well. placecats doesn't have the same random cat feature so I roughly approximated it in the example code. Closes #7966
* clarify SRP definition * Update src/content/learn/thinking-in-react.md --------- Co-authored-by: Ricky <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
@koichik ありがとうございます。作業が遅れていて申し訳ありません。 最近は毎週追従してもしょうがないので、本家で大きな更新があった場合にまとめて追従しようという感じでやっていたのですが、ちょっと別件で10月が忙しく、こちらの作業が遅れていました。 で、ご提案のフローなのですが、直感的には「いきなりやるとちょっと厳しいかも」と感じています。 追従の際は「①原文でどう更新されたのかをdiffで確認する」「②それに合わせて翻訳文を更新する」「③PRのチェックボックスをチェックする」という作業をひたすら繰り返すことになりますが、正直このうち②の部分は大した作業ではありません。どちらかというと①の部分で何が起きているか確実に把握したり、③を確実に実行して漏れをなくす、みたいな部分が大変です。 40ファイルのコンフリクトというのは珍しい話ではなく、なんだかんだ1~2時間くらいの単純作業で解決する規模なので、一旦こちらで追従を完遂して、その後にこちらのフローを小規模から試すような形でお願いできないでしょうか。 それと別に、メンテナ間で相談できる体制が一切ないのも問題なので、なにか考えたいですね… |
|
多分ちょっと工夫すればこのフロー自体のAI化もそろそろ可能だと思います(初期のClaude Codeで10分くらい試したときは諦めましたが)ので、みんなで頑張るよりはそっちの方向で工夫する方が現実的かもしれないと思っています。 |
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
110.56 KB (🟡 +98 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 |
130.43 KB (🟢 -36 B) |
240.99 KB |
/500 |
130.44 KB (🟢 -35 B) |
241 KB |
/[[...markdownPath]] |
133.21 KB (🟡 +435 B) |
243.77 KB |
/errors |
130.68 KB (🟢 -34 B) |
241.24 KB |
/errors/[errorCode] |
130.66 KB (🟢 -34 B) |
241.22 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR synchronizes the Japanese translation repository with the upstream react.dev repository at commit f8c81a0. The changes primarily include:
- Package dependency updates (React Compiler from beta to v1.0, new ESLint plugin for local rules)
- Addition of new copyright headers to source files
- Version bump from React 19.1 to 19.2
- Addition of new API documentation and sidebar entries
- New redirect rules in vercel.json
- Addition of compiler validation markers to code examples
Reviewed Changes
Copilot reviewed 254 out of 289 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| yarn.lock | Updated React Compiler plugin from beta to v1.0 and added local ESLint plugin |
| vercel.json | Added redirects for experimental_useEffectEvent and blog post URLs |
| tailwind.config.js | Added Meta copyright header |
| src/utils/* | Added Meta copyright headers to multiple utility files |
| src/siteConfig.js | Updated React version from 19.1 to 19.2 |
| src/sidebarReference.json | Added new API entries and reorganized sections for React Compiler and ESLint plugin documentation |
| src/sidebarHome.json | Added new "Setup" page entry |
| src/sidebarBlog.json | Added React Conf 2025, React Compiler v1.0, and React Foundation blog entries |
| src/pages/* | Added Meta copyright headers to page components |
| src/content/versions.md | Updated to reflect React 19.2 release |
| src/content/reference/* | Added compiler error markers and updated documentation references |
| src/content/learn/* | Added compiler error markers to code examples |
Comments suppressed due to low confidence (7)
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
見ます! |
src/content/reference/react-dom/static/prerenderToNodeStream.md
Outdated
Show resolved
Hide resolved
Co-authored-by: honey32 <[email protected]>
|
@honey32 全部そのまま対応しましたー |
This PR was automatically generated.
Merge changes from react.dev at f8c81a0
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.