diff --git a/.eslintrc b/.eslintrc
index 7bc6ab93..935fa2f2 100644
--- a/.eslintrc
+++ b/.eslintrc
@@ -9,7 +9,8 @@
"react-hooks/exhaustive-deps": "error",
"react/no-unknown-property": ["error", {"ignore": ["meta"]}],
"react-compiler/react-compiler": "error",
- "local-rules/lint-markdown-code-blocks": "error"
+ "local-rules/lint-markdown-code-blocks": "error",
+ "no-trailing-spaces": "error"
},
"env": {
"node": true,
diff --git a/next.config.js b/next.config.js
index f8ec196e..c8d7bf0e 100644
--- a/next.config.js
+++ b/next.config.js
@@ -22,10 +22,15 @@ const nextConfig = {
async rewrites() {
return {
beforeFiles: [
+ // Explicit .md extension also serves markdown
+ {
+ source: '/:path*.md',
+ destination: '/api/md/:path*',
+ },
// Serve markdown when Accept header prefers text/markdown
// Useful for LLM agents - https://www.skeptrune.com/posts/use-the-accept-header-to-serve-markdown-instead-of-html-to-llms/
{
- source: '/:path((?!llms.txt).*)',
+ source: '/:path((?!llms\\.txt|api/md).*)',
has: [
{
type: 'header',
@@ -35,11 +40,6 @@ const nextConfig = {
],
destination: '/api/md/:path*',
},
- // Explicit .md extension also serves markdown
- {
- source: '/:path*.md',
- destination: '/api/md/:path*',
- },
],
};
},
diff --git a/public/images/docs/scientists/1bX5QH6.jpg b/public/images/docs/scientists/1bX5QH6.jpg
new file mode 100644
index 00000000..630b91bd
Binary files /dev/null and b/public/images/docs/scientists/1bX5QH6.jpg differ
diff --git a/public/images/docs/scientists/1bX5QH6b.jpg b/public/images/docs/scientists/1bX5QH6b.jpg
new file mode 100644
index 00000000..7bd07436
Binary files /dev/null and b/public/images/docs/scientists/1bX5QH6b.jpg differ
diff --git a/public/images/docs/scientists/1bX5QH6s.jpg b/public/images/docs/scientists/1bX5QH6s.jpg
new file mode 100644
index 00000000..0bc3a6f4
Binary files /dev/null and b/public/images/docs/scientists/1bX5QH6s.jpg differ
diff --git a/public/images/docs/scientists/2heNQDcm.jpg b/public/images/docs/scientists/2heNQDcm.jpg
new file mode 100644
index 00000000..ecc8ab39
Binary files /dev/null and b/public/images/docs/scientists/2heNQDcm.jpg differ
diff --git a/public/images/docs/scientists/3aIiwfm.jpg b/public/images/docs/scientists/3aIiwfm.jpg
new file mode 100644
index 00000000..e93d8c80
Binary files /dev/null and b/public/images/docs/scientists/3aIiwfm.jpg differ
diff --git a/public/images/docs/scientists/5qwVYb1.jpeg b/public/images/docs/scientists/5qwVYb1.jpeg
new file mode 100644
index 00000000..cd8b4e55
Binary files /dev/null and b/public/images/docs/scientists/5qwVYb1.jpeg differ
diff --git a/public/images/docs/scientists/6o5Vuyu.jpg b/public/images/docs/scientists/6o5Vuyu.jpg
new file mode 100644
index 00000000..941563f8
Binary files /dev/null and b/public/images/docs/scientists/6o5Vuyu.jpg differ
diff --git a/public/images/docs/scientists/7vQD0fPb.jpg b/public/images/docs/scientists/7vQD0fPb.jpg
new file mode 100644
index 00000000..71baab95
Binary files /dev/null and b/public/images/docs/scientists/7vQD0fPb.jpg differ
diff --git a/public/images/docs/scientists/7vQD0fPs.jpg b/public/images/docs/scientists/7vQD0fPs.jpg
new file mode 100644
index 00000000..5da6b45f
Binary files /dev/null and b/public/images/docs/scientists/7vQD0fPs.jpg differ
diff --git a/public/images/docs/scientists/9EAYZrtl.jpg b/public/images/docs/scientists/9EAYZrtl.jpg
new file mode 100644
index 00000000..7313ffdb
Binary files /dev/null and b/public/images/docs/scientists/9EAYZrtl.jpg differ
diff --git a/public/images/docs/scientists/AlHTAdDm.jpg b/public/images/docs/scientists/AlHTAdDm.jpg
new file mode 100644
index 00000000..735c29cd
Binary files /dev/null and b/public/images/docs/scientists/AlHTAdDm.jpg differ
diff --git a/public/images/docs/scientists/DgXHVwul.jpg b/public/images/docs/scientists/DgXHVwul.jpg
new file mode 100644
index 00000000..a9dba869
Binary files /dev/null and b/public/images/docs/scientists/DgXHVwul.jpg differ
diff --git a/public/images/docs/scientists/FJeJR8M.jpg b/public/images/docs/scientists/FJeJR8M.jpg
new file mode 100644
index 00000000..433fc350
Binary files /dev/null and b/public/images/docs/scientists/FJeJR8M.jpg differ
diff --git a/public/images/docs/scientists/HMFmH6m.jpg b/public/images/docs/scientists/HMFmH6m.jpg
new file mode 100644
index 00000000..ac0a5f6c
Binary files /dev/null and b/public/images/docs/scientists/HMFmH6m.jpg differ
diff --git a/public/images/docs/scientists/IOjWm71s.jpg b/public/images/docs/scientists/IOjWm71s.jpg
new file mode 100644
index 00000000..af912e34
Binary files /dev/null and b/public/images/docs/scientists/IOjWm71s.jpg differ
diff --git a/public/images/docs/scientists/JBbMpWY.jpg b/public/images/docs/scientists/JBbMpWY.jpg
new file mode 100644
index 00000000..a59002bc
Binary files /dev/null and b/public/images/docs/scientists/JBbMpWY.jpg differ
diff --git a/public/images/docs/scientists/K9HVAGHl.jpg b/public/images/docs/scientists/K9HVAGHl.jpg
new file mode 100644
index 00000000..03894f39
Binary files /dev/null and b/public/images/docs/scientists/K9HVAGHl.jpg differ
diff --git a/public/images/docs/scientists/MK3eW3Am.jpg b/public/images/docs/scientists/MK3eW3Am.jpg
new file mode 100644
index 00000000..53287dd0
Binary files /dev/null and b/public/images/docs/scientists/MK3eW3Am.jpg differ
diff --git a/public/images/docs/scientists/MK3eW3As.jpg b/public/images/docs/scientists/MK3eW3As.jpg
new file mode 100644
index 00000000..43244d0c
Binary files /dev/null and b/public/images/docs/scientists/MK3eW3As.jpg differ
diff --git a/public/images/docs/scientists/Mx7dA2Y.jpg b/public/images/docs/scientists/Mx7dA2Y.jpg
new file mode 100644
index 00000000..ee41fbba
Binary files /dev/null and b/public/images/docs/scientists/Mx7dA2Y.jpg differ
diff --git a/public/images/docs/scientists/OKS67lhb.jpg b/public/images/docs/scientists/OKS67lhb.jpg
new file mode 100644
index 00000000..71d2917a
Binary files /dev/null and b/public/images/docs/scientists/OKS67lhb.jpg differ
diff --git a/public/images/docs/scientists/OKS67lhm.jpg b/public/images/docs/scientists/OKS67lhm.jpg
new file mode 100644
index 00000000..9fe8f630
Binary files /dev/null and b/public/images/docs/scientists/OKS67lhm.jpg differ
diff --git a/public/images/docs/scientists/OKS67lhs.jpg b/public/images/docs/scientists/OKS67lhs.jpg
new file mode 100644
index 00000000..fb3cf212
Binary files /dev/null and b/public/images/docs/scientists/OKS67lhs.jpg differ
diff --git a/public/images/docs/scientists/QIrZWGIs.jpg b/public/images/docs/scientists/QIrZWGIs.jpg
new file mode 100644
index 00000000..2bfa8ab8
Binary files /dev/null and b/public/images/docs/scientists/QIrZWGIs.jpg differ
diff --git a/public/images/docs/scientists/QwUKKmF.jpg b/public/images/docs/scientists/QwUKKmF.jpg
new file mode 100644
index 00000000..05aa061e
Binary files /dev/null and b/public/images/docs/scientists/QwUKKmF.jpg differ
diff --git a/public/images/docs/scientists/RCwLEoQm.jpg b/public/images/docs/scientists/RCwLEoQm.jpg
new file mode 100644
index 00000000..4d7d0b6d
Binary files /dev/null and b/public/images/docs/scientists/RCwLEoQm.jpg differ
diff --git a/public/images/docs/scientists/Sd1AgUOm.jpg b/public/images/docs/scientists/Sd1AgUOm.jpg
new file mode 100644
index 00000000..b81b83d2
Binary files /dev/null and b/public/images/docs/scientists/Sd1AgUOm.jpg differ
diff --git a/public/images/docs/scientists/Y3utgTi.jpg b/public/images/docs/scientists/Y3utgTi.jpg
new file mode 100644
index 00000000..8d44e4fe
Binary files /dev/null and b/public/images/docs/scientists/Y3utgTi.jpg differ
diff --git a/public/images/docs/scientists/YfeOqp2b.jpg b/public/images/docs/scientists/YfeOqp2b.jpg
new file mode 100644
index 00000000..44e0c65c
Binary files /dev/null and b/public/images/docs/scientists/YfeOqp2b.jpg differ
diff --git a/public/images/docs/scientists/YfeOqp2s.jpg b/public/images/docs/scientists/YfeOqp2s.jpg
new file mode 100644
index 00000000..19ef1570
Binary files /dev/null and b/public/images/docs/scientists/YfeOqp2s.jpg differ
diff --git a/public/images/docs/scientists/ZF6s192.jpg b/public/images/docs/scientists/ZF6s192.jpg
new file mode 100644
index 00000000..f50c7e34
Binary files /dev/null and b/public/images/docs/scientists/ZF6s192.jpg differ
diff --git a/public/images/docs/scientists/ZF6s192m.jpg b/public/images/docs/scientists/ZF6s192m.jpg
new file mode 100644
index 00000000..056f8d52
Binary files /dev/null and b/public/images/docs/scientists/ZF6s192m.jpg differ
diff --git a/public/images/docs/scientists/ZfQOOzfl.jpg b/public/images/docs/scientists/ZfQOOzfl.jpg
new file mode 100644
index 00000000..5c9e249b
Binary files /dev/null and b/public/images/docs/scientists/ZfQOOzfl.jpg differ
diff --git a/public/images/docs/scientists/aTtVpES.jpg b/public/images/docs/scientists/aTtVpES.jpg
new file mode 100644
index 00000000..00e09d09
Binary files /dev/null and b/public/images/docs/scientists/aTtVpES.jpg differ
diff --git a/public/images/docs/scientists/aeO3rpIl.jpg b/public/images/docs/scientists/aeO3rpIl.jpg
new file mode 100644
index 00000000..3b535b07
Binary files /dev/null and b/public/images/docs/scientists/aeO3rpIl.jpg differ
diff --git a/public/images/docs/scientists/bE7W1jis.jpg b/public/images/docs/scientists/bE7W1jis.jpg
new file mode 100644
index 00000000..a15a897e
Binary files /dev/null and b/public/images/docs/scientists/bE7W1jis.jpg differ
diff --git a/public/images/docs/scientists/dB2LRbj.jpg b/public/images/docs/scientists/dB2LRbj.jpg
new file mode 100644
index 00000000..f2ac0482
Binary files /dev/null and b/public/images/docs/scientists/dB2LRbj.jpg differ
diff --git a/public/images/docs/scientists/jA8hHMpm.jpg b/public/images/docs/scientists/jA8hHMpm.jpg
new file mode 100644
index 00000000..ba2168f8
Binary files /dev/null and b/public/images/docs/scientists/jA8hHMpm.jpg differ
diff --git a/public/images/docs/scientists/kxsph5Cl.jpg b/public/images/docs/scientists/kxsph5Cl.jpg
new file mode 100644
index 00000000..f3336072
Binary files /dev/null and b/public/images/docs/scientists/kxsph5Cl.jpg differ
diff --git a/public/images/docs/scientists/lICfvbD.jpg b/public/images/docs/scientists/lICfvbD.jpg
new file mode 100644
index 00000000..67393f31
Binary files /dev/null and b/public/images/docs/scientists/lICfvbD.jpg differ
diff --git a/public/images/docs/scientists/lrWQx8ls.jpg b/public/images/docs/scientists/lrWQx8ls.jpg
new file mode 100644
index 00000000..bc0708bd
Binary files /dev/null and b/public/images/docs/scientists/lrWQx8ls.jpg differ
diff --git a/public/images/docs/scientists/mynHUSas.jpg b/public/images/docs/scientists/mynHUSas.jpg
new file mode 100644
index 00000000..e369df8c
Binary files /dev/null and b/public/images/docs/scientists/mynHUSas.jpg differ
diff --git a/public/images/docs/scientists/okTpbHhm.jpg b/public/images/docs/scientists/okTpbHhm.jpg
new file mode 100644
index 00000000..a96c5c03
Binary files /dev/null and b/public/images/docs/scientists/okTpbHhm.jpg differ
diff --git a/public/images/docs/scientists/rN7hY6om.jpg b/public/images/docs/scientists/rN7hY6om.jpg
new file mode 100644
index 00000000..3c7afe1f
Binary files /dev/null and b/public/images/docs/scientists/rN7hY6om.jpg differ
diff --git a/public/images/docs/scientists/rTqKo46l.jpg b/public/images/docs/scientists/rTqKo46l.jpg
new file mode 100644
index 00000000..4a0b3dc3
Binary files /dev/null and b/public/images/docs/scientists/rTqKo46l.jpg differ
diff --git a/public/images/docs/scientists/szV5sdGb.jpg b/public/images/docs/scientists/szV5sdGb.jpg
new file mode 100644
index 00000000..8d657940
Binary files /dev/null and b/public/images/docs/scientists/szV5sdGb.jpg differ
diff --git a/public/images/docs/scientists/szV5sdGs.jpg b/public/images/docs/scientists/szV5sdGs.jpg
new file mode 100644
index 00000000..fc3c3426
Binary files /dev/null and b/public/images/docs/scientists/szV5sdGs.jpg differ
diff --git a/public/images/docs/scientists/wIdGuZwm.png b/public/images/docs/scientists/wIdGuZwm.png
new file mode 100644
index 00000000..5f482def
Binary files /dev/null and b/public/images/docs/scientists/wIdGuZwm.png differ
diff --git a/public/images/docs/scientists/yXOvdOSs.jpg b/public/images/docs/scientists/yXOvdOSs.jpg
new file mode 100644
index 00000000..0a326951
Binary files /dev/null and b/public/images/docs/scientists/yXOvdOSs.jpg differ
diff --git a/public/images/docs/scientists/z08o2TS.jpg b/public/images/docs/scientists/z08o2TS.jpg
new file mode 100644
index 00000000..42a0a00e
Binary files /dev/null and b/public/images/docs/scientists/z08o2TS.jpg differ
diff --git a/src/content/blog/2023/03/16/introducing-react-dev.md b/src/content/blog/2023/03/16/introducing-react-dev.md
index f971ddaf..96d2a630 100644
--- a/src/content/blog/2023/03/16/introducing-react-dev.md
+++ b/src/content/blog/2023/03/16/introducing-react-dev.md
@@ -279,17 +279,17 @@ export default function PackingList() {
Sally Ride's Packing List
-
-
-
@@ -317,17 +317,17 @@ export default function PackingList() {
Sally Ride's Packing List
-
-
-
@@ -365,17 +365,17 @@ export default function PackingList() {
Sally Ride's Packing List
-
-
-
@@ -409,17 +409,17 @@ export default function PackingList() {
Sally Ride's Packing List
-
-
-
diff --git a/src/content/blog/2024/02/15/react-labs-what-we-have-been-working-on-february-2024.md b/src/content/blog/2024/02/15/react-labs-what-we-have-been-working-on-february-2024.md
index c3ab47fa..002dae2a 100644
--- a/src/content/blog/2024/02/15/react-labs-what-we-have-been-working-on-february-2024.md
+++ b/src/content/blog/2024/02/15/react-labs-what-we-have-been-working-on-february-2024.md
@@ -49,19 +49,19 @@ We refer to this broader collection of features as simply "Actions". Actions all
The `action` function can operate synchronously or asynchronously. You can define them on the client side using standard JavaScript or on the server with the [`'use server'`](/reference/rsc/use-server) directive. When using an action, React will manage the life cycle of the data submission for you, providing hooks like [`useFormStatus`](/reference/react-dom/hooks/useFormStatus), and [`useActionState`](/reference/react/useActionState) to access the current state and response of the form action.
-By default, Actions are submitted within a [transition](/reference/react/useTransition), keeping the current page interactive while the action is processing. Since Actions support async functions, we've also added the ability to use `async/await` in transitions. This allows you to show pending UI with the `isPending` state of a transition when an async request like `fetch` starts, and show the pending UI all the way through the update being applied.
+By default, Actions are submitted within a [transition](/reference/react/useTransition), keeping the current page interactive while the action is processing. Since Actions support async functions, we've also added the ability to use `async/await` in transitions. This allows you to show pending UI with the `isPending` state of a transition when an async request like `fetch` starts, and show the pending UI all the way through the update being applied.
Alongside Actions, we're introducing a feature named [`useOptimistic`](/reference/react/useOptimistic) for managing optimistic state updates. With this hook, you can apply temporary updates that are automatically reverted once the final state commits. For Actions, this allows you to optimistically set the final state of the data on the client, assuming the submission is successful, and revert to the value for data received from the server. It works using regular `async`/`await`, so it works the same whether you're using `fetch` on the client, or a Server Action from the server.
Library authors can implement custom `action={fn}` props in their own components with `useTransition`. Our intent is for libraries to adopt the Actions pattern when designing their component APIs, to provide a consistent experience for React developers. For example, if your library provides a `` component, consider also exposing a `` API, too.
-While we initially focused on Server Actions for client-server data transfer, our philosophy for React is to provide the same programming model across all platforms and environments. When possible, if we introduce a feature on the client, we aim to make it also work on the server, and vice versa. This philosophy allows us to create a single set of APIs that work no matter where your app runs, making it easier to upgrade to different environments later.
+While we initially focused on Server Actions for client-server data transfer, our philosophy for React is to provide the same programming model across all platforms and environments. When possible, if we introduce a feature on the client, we aim to make it also work on the server, and vice versa. This philosophy allows us to create a single set of APIs that work no matter where your app runs, making it easier to upgrade to different environments later.
Actions are now available in the Canary channel and will ship in the next release of React.
## New Features in React Canary {/*new-features-in-react-canary*/}
-We introduced [React Canaries](/blog/2023/05/03/react-canaries) as an option to adopt individual new stable features as soon as their design is close to final, before they’re released in a stable semver version.
+We introduced [React Canaries](/blog/2023/05/03/react-canaries) as an option to adopt individual new stable features as soon as their design is close to final, before they’re released in a stable semver version.
Canaries are a change to the way we develop React. Previously, features would be researched and built privately inside of Meta, so users would only see the final polished product when released to Stable. With Canaries, we’re building in public with the help of the community to finalize features we share in the React Labs blog series. This means you hear about new features sooner, as they’re being finalized instead of after they’re complete.
@@ -75,7 +75,7 @@ React Server Components, Asset Loading, Document Metadata, and Actions have all
- **Actions**: As shared above, we've added Actions to manage sending data from the client to the server. You can add `action` to elements like [``](/reference/react-dom/components/form), access the status with [`useFormStatus`](/reference/react-dom/hooks/useFormStatus), handle the result with [`useActionState`](/reference/react/useActionState), and optimistically update the UI with [`useOptimistic`](/reference/react/useOptimistic).
-Since all of these features work together, it’s difficult to release them in the Stable channel individually. Releasing Actions without the complementary hooks for accessing form states would limit the practical usability of Actions. Introducing React Server Components without integrating Server Actions would complicate modifying data on the server.
+Since all of these features work together, it’s difficult to release them in the Stable channel individually. Releasing Actions without the complementary hooks for accessing form states would limit the practical usability of Actions. Introducing React Server Components without integrating Server Actions would complicate modifying data on the server.
Before we can release a set of features to the Stable channel, we need to ensure they work cohesively and developers have everything they need to use them in production. React Canaries allow us to develop these features individually, and release the stable APIs incrementally until the entire feature set is complete.
diff --git a/src/content/blog/2024/04/25/react-19-upgrade-guide.md b/src/content/blog/2024/04/25/react-19-upgrade-guide.md
index cb83a617..1823ebdf 100644
--- a/src/content/blog/2024/04/25/react-19-upgrade-guide.md
+++ b/src/content/blog/2024/04/25/react-19-upgrade-guide.md
@@ -20,7 +20,7 @@ The improvements added to React 19 require some breaking changes, but we've work
#### React 18.3 has also been published {/*react-18-3*/}
-To help make the upgrade to React 19 easier, we've published a `react@18.3` release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.
+To help make the upgrade to React 19 easier, we've published a `react@18.3` release that is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.
We recommend upgrading to React 18.3 first to help identify any issues before upgrading to React 19.
@@ -109,17 +109,17 @@ npx codemod@latest react/19/migration-recipe
```
This will run the following codemods from `react-codemod`:
-- [`replace-reactdom-render`](https://github.com/reactjs/react-codemod?tab=readme-ov-file#replace-reactdom-render)
+- [`replace-reactdom-render`](https://github.com/reactjs/react-codemod?tab=readme-ov-file#replace-reactdom-render)
- [`replace-string-ref`](https://github.com/reactjs/react-codemod?tab=readme-ov-file#replace-string-ref)
- [`replace-act-import`](https://github.com/reactjs/react-codemod?tab=readme-ov-file#replace-act-import)
-- [`replace-use-form-state`](https://github.com/reactjs/react-codemod?tab=readme-ov-file#replace-use-form-state)
+- [`replace-use-form-state`](https://github.com/reactjs/react-codemod?tab=readme-ov-file#replace-use-form-state)
- [`prop-types-typescript`](https://github.com/reactjs/react-codemod#react-proptypes-to-prop-types)
This does not include the TypeScript changes. See [TypeScript changes](#typescript-changes) below.
-Changes that include a codemod include the command below.
+Changes that include a codemod include the command below.
For a list of all available codemods, see the [`react-codemod` repo](https://github.com/reactjs/react-codemod).
@@ -127,7 +127,7 @@ For a list of all available codemods, see the [`react-codemod` repo](https://git
### Errors in render are not re-thrown {/*errors-in-render-are-not-re-thrown*/}
-In previous versions of React, errors thrown during render were caught and rethrown. In DEV, we would also log to `console.error`, resulting in duplicate error logs.
+In previous versions of React, errors thrown during render were caught and rethrown. In DEV, we would also log to `console.error`, resulting in duplicate error logs.
In React 19, we've [improved how errors are handled](/blog/2024/04/25/react-19#error-handling) to reduce duplication by not re-throwing:
@@ -348,7 +348,7 @@ npm install react-shallow-renderer --save-dev
##### Please reconsider shallow rendering {/*please-reconsider-shallow-rendering*/}
-Shallow rendering depends on React internals and can block you from future upgrades. We recommend migrating your tests to [@testing-library/react](https://testing-library.com/docs/react-testing-library/intro/) or [@testing-library/react-native](https://testing-library.com/docs/react-native-testing-library/intro).
+Shallow rendering depends on React internals and can block you from future upgrades. We recommend migrating your tests to [@testing-library/react](https://testing-library.com/docs/react-testing-library/intro/) or [@testing-library/react-native](https://testing-library.com/docs/react-native-testing-library/intro).
@@ -465,7 +465,7 @@ npx codemod@latest react/19/replace-reactdom-render
#### Removed: `ReactDOM.findDOMNode` {/*removed-reactdom-finddomnode*/}
-`ReactDOM.findDOMNode` was [deprecated in October 2018 (v16.6.0)](https://legacy.reactjs.org/blog/2018/10/23/react-v-16-6.html#deprecations-in-strictmode).
+`ReactDOM.findDOMNode` was [deprecated in October 2018 (v16.6.0)](https://legacy.reactjs.org/blog/2018/10/23/react-v-16-6.html#deprecations-in-strictmode).
We're removing `findDOMNode` because it was a legacy escape hatch that was slow to execute, fragile to refactoring, only returned the first child, and broke abstraction levels (see more [here](https://legacy.reactjs.org/docs/strict-mode.html#warning-about-deprecated-finddomnode-usage)). You can replace `ReactDOM.findDOMNode` with [DOM refs](/learn/manipulating-the-dom-with-refs):
@@ -551,7 +551,7 @@ This change means Suspense fallbacks display faster, while still warming lazy re
### UMD builds removed {/*umd-builds-removed*/}
-UMD was widely used in the past as a convenient way to load React without a build step. Now, there are modern alternatives for loading modules as scripts in HTML documents. Starting with React 19, React will no longer produce UMD builds to reduce the complexity of its testing and release process.
+UMD was widely used in the past as a convenient way to load React without a build step. Now, there are modern alternatives for loading modules as scripts in HTML documents. Starting with React 19, React will no longer produce UMD builds to reduce the complexity of its testing and release process.
To load React 19 with a script tag, we recommend using an ESM-based CDN such as [esm.sh](https://esm.sh/).
@@ -569,7 +569,7 @@ This release includes changes to React internals that may impact libraries that
Based on our [Versioning Policy](https://react.dev/community/versioning-policy#what-counts-as-a-breaking-change), these updates are not listed as breaking changes, and we are not including docs for how to upgrade them. The recommendation is to remove any code that depends on internals.
-To reflect the impact of using internals, we have renamed the `SECRET_INTERNALS` suffix to:
+To reflect the impact of using internals, we have renamed the `SECRET_INTERNALS` suffix to:
`_DO_NOT_USE_OR_WARN_USERS_THEY_CANNOT_UPGRADE`
diff --git a/src/content/blog/2024/12/05/react-19.md b/src/content/blog/2024/12/05/react-19.md
index 4e9aad8e..74964645 100644
--- a/src/content/blog/2024/12/05/react-19.md
+++ b/src/content/blog/2024/12/05/react-19.md
@@ -59,7 +59,7 @@ function UpdateName({}) {
if (error) {
setError(error);
return;
- }
+ }
redirect("/path");
};
@@ -92,7 +92,7 @@ function UpdateName({}) {
if (error) {
setError(error);
return;
- }
+ }
redirect("/path");
})
};
@@ -176,7 +176,7 @@ const [error, submitAction, isPending] = useActionState(
);
```
-`useActionState` accepts a function (the "Action"), and returns a wrapped Action to call. This works because Actions compose. When the wrapped Action is called, `useActionState` will return the last result of the Action as `data`, and the pending state of the Action as `pending`.
+`useActionState` accepts a function (the "Action"), and returns a wrapped Action to call. This works because Actions compose. When the wrapped Action is called, `useActionState` will return the last result of the Action as `data`, and the pending state of the Action as `pending`.
@@ -308,7 +308,7 @@ function Heading({children}) {
if (children == null) {
return null;
}
-
+
// This would not work with useContext
// because of the early return.
const theme = use(ThemeContext);
@@ -330,7 +330,7 @@ We've added two new APIs to `react-dom/static` for static site generation:
- [`prerender`](/reference/react-dom/static/prerender)
- [`prerenderToNodeStream`](/reference/react-dom/static/prerenderToNodeStream)
-These new APIs improve on `renderToString` by waiting for data to load for static HTML generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. For example, in a Web Stream environment, you can prerender a React tree to static HTML with `prerender`:
+These new APIs improve on `renderToString` by waiting for data to load for static HTML generation. They are designed to work with streaming environments like Node.js Streams and Web Streams. For example, in a Web Stream environment, you can prerender a React tree to static HTML with `prerender`:
```js
import { prerender } from 'react-dom/static';
@@ -355,14 +355,14 @@ For more information, see [React DOM Static APIs](/reference/react-dom/static).
Server Components are a new option that allows rendering components ahead of time, before bundling, in an environment separate from your client application or SSR server. This separate environment is the "server" in React Server Components. Server Components can run once at build time on your CI server, or they can be run for each request using a web server.
-React 19 includes all of the React Server Components features included from the Canary channel. This means libraries that ship with Server Components can now target React 19 as a peer dependency with a `react-server` [export condition](https://github.com/reactjs/rfcs/blob/main/text/0227-server-module-conventions.md#react-server-conditional-exports) for use in frameworks that support the [Full-stack React Architecture](/learn/creating-a-react-app#which-features-make-up-the-react-teams-full-stack-architecture-vision).
+React 19 includes all of the React Server Components features included from the Canary channel. This means libraries that ship with Server Components can now target React 19 as a peer dependency with a `react-server` [export condition](https://github.com/reactjs/rfcs/blob/main/text/0227-server-module-conventions.md#react-server-conditional-exports) for use in frameworks that support the [Full-stack React Architecture](/learn/creating-a-react-app#which-features-make-up-the-react-teams-full-stack-architecture-vision).
#### How do I build support for Server Components? {/*how-do-i-build-support-for-server-components*/}
-While React Server Components in React 19 are stable and will not break between minor versions, the underlying APIs used to implement a React Server Components bundler or framework do not follow semver and may break between minors in React 19.x.
+While React Server Components in React 19 are stable and will not break between minor versions, the underlying APIs used to implement a React Server Components bundler or framework do not follow semver and may break between minors in React 19.x.
To support React Server Components as a bundler or framework, we recommend pinning to a specific React version, or using the Canary release. We will continue working with bundlers and frameworks to stabilize the APIs used to implement React Server Components in the future.
@@ -497,7 +497,7 @@ function App({children}) {
{children}
- );
+ );
}
```
@@ -521,7 +521,7 @@ We now support returning a cleanup function from `ref` callbacks:
/>
```
-When the component unmounts, React will call the cleanup function returned from the `ref` callback. This works for DOM refs, refs to class components, and `useImperativeHandle`.
+When the component unmounts, React will call the cleanup function returned from the `ref` callback. This works for DOM refs, refs to class components, and `useImperativeHandle`.
@@ -551,7 +551,7 @@ function Search({deferredValue}) {
// On initial render the value is ''.
// Then a re-render is scheduled with the deferredValue.
const value = useDeferredValue(deferredValue, '');
-
+
return (
);
@@ -564,7 +564,7 @@ For more, see [`useDeferredValue`](/reference/react/useDeferredValue).
### Support for Document Metadata {/*support-for-metadata-tags*/}
-In HTML, document metadata tags like ``, ``, and `` are reserved for placement in the `` section of the document. In React, the component that decides what metadata is appropriate for the app may be very far from the place where you render the `` or React does not render the `` at all. In the past, these elements would need to be inserted manually in an effect, or by libraries like [`react-helmet`](https://github.com/nfl/react-helmet), and required careful handling when server rendering a React application.
+In HTML, document metadata tags like ``, ``, and `` are reserved for placement in the `` section of the document. In React, the component that decides what metadata is appropriate for the app may be very far from the place where you render the `` or React does not render the `` at all. In the past, these elements would need to be inserted manually in an effect, or by libraries like [`react-helmet`](https://github.com/nfl/react-helmet), and required careful handling when server rendering a React application.
In React 19, we're adding support for rendering document metadata tags in components natively:
@@ -726,7 +726,7 @@ In React 19, unexpected tags in the `` and `` will be skipped over,
### Better error reporting {/*error-handling*/}
-We improved error handling in React 19 to remove duplication and provide options for handling caught and uncaught errors. For example, when there's an error in render caught by an Error Boundary, previously React would throw the error twice (once for the original error, then again after failing to automatically recover), and then call `console.error` with info about where the error occurred.
+We improved error handling in React 19 to remove duplication and provide options for handling caught and uncaught errors. For example, when there's an error in render caught by an Error Boundary, previously React would throw the error twice (once for the original error, then again after failing to automatically recover), and then call `console.error` with info about where the error occurred.
This resulted in three errors for every caught error:
diff --git a/src/content/blog/2025/02/14/sunsetting-create-react-app.md b/src/content/blog/2025/02/14/sunsetting-create-react-app.md
index 6f3e95d8..45c0090d 100644
--- a/src/content/blog/2025/02/14/sunsetting-create-react-app.md
+++ b/src/content/blog/2025/02/14/sunsetting-create-react-app.md
@@ -11,7 +11,7 @@ February 14, 2025 by [Matt Carroll](https://twitter.com/mattcarrollcode) and [Ri
-Today, we’re deprecating [Create React App](https://create-react-app.dev/) for new apps, and encouraging existing apps to migrate to a [framework](#how-to-migrate-to-a-framework), or to [migrate to a build tool](#how-to-migrate-to-a-build-tool) like Vite, Parcel, or RSBuild.
+Today, we’re deprecating [Create React App](https://create-react-app.dev/) for new apps, and encouraging existing apps to migrate to a [framework](#how-to-migrate-to-a-framework), or to [migrate to a build tool](#how-to-migrate-to-a-build-tool) like Vite, Parcel, or RSBuild.
We’re also providing docs for when a framework isn’t a good fit for your project, you want to build your own framework, or you just want to learn how React works by [building a React app from scratch](/learn/build-a-react-app-from-scratch).
@@ -75,7 +75,7 @@ To help get started with Vite, Parcel or Rsbuild, we've added new docs for [Buil
#### Do I need a framework? {/*do-i-need-a-framework*/}
-Most apps would benefit from a framework, but there are valid cases to build a React app from scratch. A good rule of thumb is if your app needs routing, you would probably benefit from a framework.
+Most apps would benefit from a framework, but there are valid cases to build a React app from scratch. A good rule of thumb is if your app needs routing, you would probably benefit from a framework.
Just like Svelte has Sveltekit, Vue has Nuxt, and Solid has SolidStart, [React recommends using a framework](#why-we-recommend-frameworks) that fully integrates routing into features like data-fetching and code-splitting out of the box. This avoids the pain of needing to write your own complex configurations and essentially build a framework yourself.
diff --git a/src/content/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components.md b/src/content/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components.md
index dc049c78..70e5c2e6 100644
--- a/src/content/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components.md
+++ b/src/content/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components.md
@@ -176,7 +176,7 @@ The patches published today prevent stringifying the Server Function source code
Secrets hardcoded in source code may be exposed, but runtime secrets such as `process.env.SECRET` are not affected.
-The scope of the exposed code is limited to the code inside the Server Function, which may include other functions depending on the amount of inlining your bundler provides.
+The scope of the exposed code is limited to the code inside the Server Function, which may include other functions depending on the amount of inlining your bundler provides.
Always verify against production bundles.
diff --git a/src/content/community/conferences.md b/src/content/community/conferences.md
index ada81a60..2079cdd6 100644
--- a/src/content/community/conferences.md
+++ b/src/content/community/conferences.md
@@ -219,7 +219,7 @@ May 15 - 16, 2024. In-person in Henderson, NV, USA + remote
[Website](https://conf.react.dev) - [Twitter](https://twitter.com/reactjs)
### React Native Connection 2024 {/*react-native-connection-2024*/}
-April 23, 2024. In-person in Paris, France
+April 23, 2024. In-person in Paris, France
[Website](https://reactnativeconnection.io/) - [Twitter](https://twitter.com/ReactNativeConn)
@@ -261,7 +261,7 @@ October 20 & 23, 2023. In-person in London, UK + remote first interactivity (hyb
### React Brussels 2023 {/*react-brussels-2023*/}
October 13th 2023. In-person in Brussels, Belgium + Remote (hybrid)
-[Website](https://www.react.brussels/) - [Twitter](https://twitter.com/BrusselsReact) - [Videos](https://www.youtube.com/playlist?list=PL53Z0yyYnpWh85KeMomUoVz8_brrmh_aC)
+[Website](https://www.react.brussels/) - [Twitter](https://twitter.com/BrusselsReact) - [Videos](https://www.youtube.com/playlist?list=PL53Z0yyYnpWh85KeMomUoVz8_brrmh_aC)
### React India 2023 {/*react-india-2023*/}
October 5 - 7, 2023. In-person in Goa, India (hybrid event) + Oct 3 2023 - remote day
@@ -284,7 +284,7 @@ September 28 - 30, 2023. Alicante, Spain
[Website](https://reactalicante.es/) - [Twitter](https://twitter.com/reactalicante)
### RedwoodJS Conference 2023 {/*redwoodjs-conference-2023*/}
-September 26 - 29, 2023. Grants Pass, Oregon + remote (hybrid event)
+September 26 - 29, 2023. Grants Pass, Oregon + remote (hybrid event)
[Website](https://www.redwoodjsconf.com/) - [Twitter](https://twitter.com/redwoodjs)
diff --git a/src/content/community/translations.md b/src/content/community/translations.md
index 4c07e6a1..fd49bd3e 100644
--- a/src/content/community/translations.md
+++ b/src/content/community/translations.md
@@ -28,7 +28,7 @@ For the progress of each translation, see: [Is React Translated Yet?](https://tr
## How to contribute {/*how-to-contribute*/}
-You can contribute to the translation efforts!
+You can contribute to the translation efforts!
The community conducts the translation work for the React docs on each language-specific fork of react.dev. Typical translation work involves directly translating a Markdown file and creating a pull request. Click the "contribute" link above to the GitHub repository for your language, and follow the instructions there to help with the translation effort.
diff --git a/src/content/learn/adding-interactivity.md b/src/content/learn/adding-interactivity.md
index 214aa7e2..0f22bfee 100644
--- a/src/content/learn/adding-interactivity.md
+++ b/src/content/learn/adding-interactivity.md
@@ -136,6 +136,7 @@ export default function Gallery() {
```js src/data.js
export const sculptureList = [{
+<<<<<<< HEAD
name: 'Даніна нейрахірургіі',
artist: 'Марта Колвін Андрадэ',
description: 'Хаця Колвін пераважна вядомая сваімі абстрактнымі тэмамі, якія спасылаюцца на да-іспанскія сімвалы, гэтая гіганцкая скульптура, даніна павагі нейрахірургіі, з\'яўляецца адным з яе самых вядомых твораў мастацтва.',
@@ -207,6 +208,79 @@ export const sculptureList = [{
description: 'Заапарк Тайбэя заказаў плошчу бегемотаў, на якой гулялі пагружаныя ў ваду бегемоты.',
url: 'https://i.imgur.com/6o5Vuyu.jpg',
alt: 'Група бронзавых скульптур бегемотаў, якія выходзяць з тратуара, нібы яны плывуць.'
+=======
+ name: 'Homenaje a la Neurocirugía',
+ artist: 'Marta Colvin Andrade',
+ description: 'Although Colvin is predominantly known for abstract themes that allude to pre-Hispanic symbols, this gigantic sculpture, an homage to neurosurgery, is one of her most recognizable public art pieces.',
+ url: 'https://react.dev/images/docs/scientists/Mx7dA2Y.jpg',
+ alt: 'A bronze statue of two crossed hands delicately holding a human brain in their fingertips.'
+}, {
+ name: 'Floralis Genérica',
+ artist: 'Eduardo Catalano',
+ description: 'This enormous (75 ft. or 23m) silver flower is located in Buenos Aires. It is designed to move, closing its petals in the evening or when strong winds blow and opening them in the morning.',
+ url: 'https://react.dev/images/docs/scientists/ZF6s192m.jpg',
+ alt: 'A gigantic metallic flower sculpture with reflective mirror-like petals and strong stamens.'
+}, {
+ name: 'Eternal Presence',
+ artist: 'John Woodrow Wilson',
+ description: 'Wilson was known for his preoccupation with equality, social justice, as well as the essential and spiritual qualities of humankind. This massive (7ft. or 2,13m) bronze represents what he described as "a symbolic Black presence infused with a sense of universal humanity."',
+ url: 'https://react.dev/images/docs/scientists/aTtVpES.jpg',
+ alt: 'The sculpture depicting a human head seems ever-present and solemn. It radiates calm and serenity.'
+}, {
+ name: 'Moai',
+ artist: 'Unknown Artist',
+ description: 'Located on the Easter Island, there are 1,000 moai, or extant monumental statues, created by the early Rapa Nui people, which some believe represented deified ancestors.',
+ url: 'https://react.dev/images/docs/scientists/RCwLEoQm.jpg',
+ alt: 'Three monumental stone busts with the heads that are disproportionately large with somber faces.'
+}, {
+ name: 'Blue Nana',
+ artist: 'Niki de Saint Phalle',
+ description: 'The Nanas are triumphant creatures, symbols of femininity and maternity. Initially, Saint Phalle used fabric and found objects for the Nanas, and later on introduced polyester to achieve a more vibrant effect.',
+ url: 'https://react.dev/images/docs/scientists/Sd1AgUOm.jpg',
+ alt: 'A large mosaic sculpture of a whimsical dancing female figure in a colorful costume emanating joy.'
+}, {
+ name: 'Ultimate Form',
+ artist: 'Barbara Hepworth',
+ description: 'This abstract bronze sculpture is a part of The Family of Man series located at Yorkshire Sculpture Park. Hepworth chose not to create literal representations of the world but developed abstract forms inspired by people and landscapes.',
+ url: 'https://react.dev/images/docs/scientists/2heNQDcm.jpg',
+ alt: 'A tall sculpture made of three elements stacked on each other reminding of a human figure.'
+}, {
+ name: 'Cavaliere',
+ artist: 'Lamidi Olonade Fakeye',
+ description: "Descended from four generations of woodcarvers, Fakeye's work blended traditional and contemporary Yoruba themes.",
+ url: 'https://react.dev/images/docs/scientists/wIdGuZwm.png',
+ alt: 'An intricate wood sculpture of a warrior with a focused face on a horse adorned with patterns.'
+}, {
+ name: 'Big Bellies',
+ artist: 'Alina Szapocznikow',
+ description: "Szapocznikow is known for her sculptures of the fragmented body as a metaphor for the fragility and impermanence of youth and beauty. This sculpture depicts two very realistic large bellies stacked on top of each other, each around five feet (1,5m) tall.",
+ url: 'https://react.dev/images/docs/scientists/AlHTAdDm.jpg',
+ alt: 'The sculpture reminds a cascade of folds, quite different from bellies in classical sculptures.'
+}, {
+ name: 'Terracotta Army',
+ artist: 'Unknown Artist',
+ description: 'The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consisted of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.',
+ url: 'https://react.dev/images/docs/scientists/HMFmH6m.jpg',
+ alt: '12 terracotta sculptures of solemn warriors, each with a unique facial expression and armor.'
+}, {
+ name: 'Lunar Landscape',
+ artist: 'Louise Nevelson',
+ description: 'Nevelson was known for scavenging objects from New York City debris, which she would later assemble into monumental constructions. In this one, she used disparate parts like a bedpost, juggling pin, and seat fragment, nailing and gluing them into boxes that reflect the influence of Cubism’s geometric abstraction of space and form.',
+ url: 'https://react.dev/images/docs/scientists/rN7hY6om.jpg',
+ alt: 'A black matte sculpture where the individual elements are initially indistinguishable.'
+}, {
+ name: 'Aureole',
+ artist: 'Ranjani Shettar',
+ description: 'Shettar merges the traditional and the modern, the natural and the industrial. Her art focuses on the relationship between man and nature. Her work was described as compelling both abstractly and figuratively, gravity defying, and a "fine synthesis of unlikely materials."',
+ url: 'https://react.dev/images/docs/scientists/okTpbHhm.jpg',
+ alt: 'A pale wire-like sculpture mounted on concrete wall and descending on the floor. It appears light.'
+}, {
+ name: 'Hippos',
+ artist: 'Taipei Zoo',
+ description: 'The Taipei Zoo commissioned a Hippo Square featuring submerged hippos at play.',
+ url: 'https://react.dev/images/docs/scientists/6o5Vuyu.jpg',
+ alt: 'A group of bronze hippo sculptures emerging from the sett sidewalk as if they were swimming.'
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
}];
```
@@ -421,9 +495,15 @@ export default function Form() {
const [person, setPerson] = useState({
name: 'Нікі дэ Сен-Фаль',
artwork: {
+<<<<<<< HEAD
title: 'Блакітная нана',
city: 'Гамбург',
image: 'https://i.imgur.com/Sd1AgUOm.jpg',
+=======
+ title: 'Blue Nana',
+ city: 'Hamburg',
+ image: 'https://react.dev/images/docs/scientists/Sd1AgUOm.jpg',
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
}
});
@@ -529,9 +609,15 @@ export default function Form() {
const [person, updatePerson] = useImmer({
name: 'Нікі дэ Сен-Фаль',
artwork: {
+<<<<<<< HEAD
title: 'Блакітная нана',
city: 'Гамбург',
image: 'https://i.imgur.com/Sd1AgUOm.jpg',
+=======
+ title: 'Blue Nana',
+ city: 'Hamburg',
+ image: 'https://react.dev/images/docs/scientists/Sd1AgUOm.jpg',
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
}
});
diff --git a/src/content/learn/build-a-react-app-from-scratch.md b/src/content/learn/build-a-react-app-from-scratch.md
index 8a2142cf..182ad54b 100644
--- a/src/content/learn/build-a-react-app-from-scratch.md
+++ b/src/content/learn/build-a-react-app-from-scratch.md
@@ -12,7 +12,7 @@ If your app has constraints not well-served by existing frameworks, you prefer t
#### Consider using a framework {/*consider-using-a-framework*/}
-Starting from scratch is an easy way to get started using React, but a major tradeoff to be aware of is that going this route is often the same as building your own adhoc framework. As your requirements evolve, you may need to solve more framework-like problems that our recommended frameworks already have well developed and supported solutions for.
+Starting from scratch is an easy way to get started using React, but a major tradeoff to be aware of is that going this route is often the same as building your own adhoc framework. As your requirements evolve, you may need to solve more framework-like problems that our recommended frameworks already have well developed and supported solutions for.
For example, if in the future your app needs support for server-side rendering (SSR), static site generation (SSG), and/or React Server Components (RSC), you will have to implement those on your own. Similarly, future React features that require integrating at the framework level will have to be implemented on your own if you want to use them.
@@ -132,12 +132,12 @@ Since the build tool you select only supports single page apps (SPAs), you'll ne
* **React Server Components (RSC)** lets you mix build-time, server-only, and interactive components in a single React tree. RSC can improve performance, but it currently requires deep expertise to set up and maintain. See [Parcel's RSC examples](https://github.com/parcel-bundler/rsc-examples).
-Your rendering strategies need to integrate with your router so apps built with your framework can choose the rendering strategy on a per-route level. This will enable different rendering strategies without having to rewrite your whole app. For example, the landing page for your app might benefit from being statically generated (SSG), while a page with a content feed might perform best with server-side rendering.
+Your rendering strategies need to integrate with your router so apps built with your framework can choose the rendering strategy on a per-route level. This will enable different rendering strategies without having to rewrite your whole app. For example, the landing page for your app might benefit from being statically generated (SSG), while a page with a content feed might perform best with server-side rendering.
Using the right rendering strategy for the right routes can decrease the time it takes for the first byte of content to be loaded ([Time to First Byte](https://web.dev/articles/ttfb)), the first piece of content to render ([First Contentful Paint](https://web.dev/articles/fcp)), and the largest visible content of the app to render ([Largest Contentful Paint](https://web.dev/articles/lcp)).
### And more... {/*and-more*/}
-These are just a few examples of the features a new app will need to consider when building from scratch. Many limitations you'll hit can be difficult to solve as each problem is interconnected with the others and can require deep expertise in problem areas you may not be familiar with.
+These are just a few examples of the features a new app will need to consider when building from scratch. Many limitations you'll hit can be difficult to solve as each problem is interconnected with the others and can require deep expertise in problem areas you may not be familiar with.
-If you don't want to solve these problems on your own, you can [get started with a framework](/learn/creating-a-react-app) that provides these features out of the box.
+If you don't want to solve these problems on your own, you can [get started with a framework](/learn/creating-a-react-app) that provides these features out of the box.
diff --git a/src/content/learn/choosing-the-state-structure.md b/src/content/learn/choosing-the-state-structure.md
index f6ed669a..2533a53d 100644
--- a/src/content/learn/choosing-the-state-structure.md
+++ b/src/content/learn/choosing-the-state-structure.md
@@ -458,7 +458,7 @@ export default function Menu() {
return (
<>
-
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -80,6 +94,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -132,6 +160,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -236,6 +278,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -290,6 +346,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -371,6 +441,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -417,6 +501,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -474,6 +572,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -512,6 +624,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -560,6 +686,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
@@ -604,6 +744,7 @@ export default function PackingList() {
Спіс рэчаў Салі Райд
+<<<<<<< HEAD
+
+ >>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
diff --git a/src/content/learn/creating-a-react-app.md b/src/content/learn/creating-a-react-app.md
index a65b59f6..fef66838 100644
--- a/src/content/learn/creating-a-react-app.md
+++ b/src/content/learn/creating-a-react-app.md
@@ -104,7 +104,7 @@ Server Components and Suspense are React features rather than Next.js features.
If your app has constraints not well-served by existing frameworks, you prefer to build your own framework, or you just want to learn the basics of a React app, there are other options available for starting a React project from scratch.
-Starting from scratch gives you more flexibility, but does require that you make choices on which tools to use for routing, data fetching, and other common usage patterns. It's a lot like building your own framework, instead of using a framework that already exists. The [frameworks we recommend](#full-stack-frameworks) have built-in solutions for these problems.
+Starting from scratch gives you more flexibility, but does require that you make choices on which tools to use for routing, data fetching, and other common usage patterns. It's a lot like building your own framework, instead of using a framework that already exists. The [frameworks we recommend](#full-stack-frameworks) have built-in solutions for these problems.
If you want to build your own solutions, see our guide to [build a React app from Scratch](/learn/build-a-react-app-from-scratch) for instructions on how to set up a new React project starting with a build tool like [Vite](https://vite.dev/), [Parcel](https://parceljs.org/), or [RSbuild](https://rsbuild.dev/).
diff --git a/src/content/learn/describing-the-ui.md b/src/content/learn/describing-the-ui.md
index 83cbf396..ff79a4e8 100644
--- a/src/content/learn/describing-the-ui.md
+++ b/src/content/learn/describing-the-ui.md
@@ -32,7 +32,7 @@ React — гэта JavaScript бібліятэка для рэндэрынгу
function Profile() {
return (
);
@@ -98,7 +98,7 @@ export default function Gallery() {
export default function Profile() {
return (
);
@@ -131,7 +131,7 @@ export default function TodoList() {
// Гэта не будзе працаваць!
Спіс задач Хедзі Ламар
@@ -160,7 +160,7 @@ export default function TodoList() {
<>
Спіс задач Хедзі Ламар
@@ -207,7 +207,7 @@ export default function TodoList() {
Спіс задач {person.name}
@@ -282,7 +282,7 @@ function Card({ children }) {
```js src/utils.js
export function getImageUrl(person, size = 's') {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
size +
'.jpg'
@@ -435,7 +435,7 @@ export const people = [{
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
's.jpg'
);
@@ -526,9 +526,15 @@ export default function TeaSet() {
## Карыстальніцкі інтэрфейс у выглядзе дрэва {/*your-ui-as-a-tree*/}
+<<<<<<< HEAD
React выкарыстоўвае дрэвы для мадэліравання адносін паміж кампанентамі і модулямі.
Дрэва рэндэрынгу React — гэта адлюстраванне бацькоўскіх і даччыных адносін паміж кампанентамі.
+=======
+React uses trees to model the relationships between components and modules.
+
+A React render tree is a representation of the parent and child relationship between components.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
@@ -538,7 +544,11 @@ React выкарыстоўвае дрэвы для мадэліравання а
Кампаненты, якія знаходзяцца ў верхняй частцы дрэва, каля каранёвага кампанента, лічацца кампанентамі верхняга ўзроўню. Кампаненты без даччыных кампанентаў з'яўляюцца ліставымі кампанентамі. Такая класіфікацыя кампанентаў карысная для разумення патоку даных і прадукцыйнасці рэндэрынгу.
+<<<<<<< HEAD
Мадэліраванне адносін паміж модулямі JavaScript — гэта яшчэ адзін карысны спосаб зразумець вашу праграму. Мы называем гэта «дрэвам залежнасці модуляў».
+=======
+Modelling the relationship between JavaScript modules is another useful way to understand your app. We refer to it as a module dependency tree.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
@@ -546,7 +556,11 @@ React выкарыстоўвае дрэвы для мадэліравання а
+<<<<<<< HEAD
Дрэва залежнасцяў часта выкарыстоўваецца інструментамі зборкі для аб'яднання ўсяго адпаведнага JavaScript кода для спампоўвання і адлюстравання кліентам. Вялікі памер пакета пагаршае карыстальніцкі досвед узаемадзеяння з праграмамі напісанымі з дапамогай React. Разуменне дрэва залежнасцяў модуля дапамагае вырашаць такія праблемы.
+=======
+A dependency tree is often used by build tools to bundle all the relevant JavaScript code for the client to download and render. A large bundle size regresses user experience for React apps. Understanding the module dependency tree is helpful to debug such issues.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
diff --git a/src/content/learn/editor-setup.md b/src/content/learn/editor-setup.md
index ca8103b3..f8c4c9eb 100644
--- a/src/content/learn/editor-setup.md
+++ b/src/content/learn/editor-setup.md
@@ -31,7 +31,11 @@ title: Наладжванне рэдактара
### Лінтаванне {/*linting*/}
+<<<<<<< HEAD
Лінтары кода знаходзяць праблемы ў вашым кодзе падчас напісання, дапамагаючы вам выправіць іх на ранняй стадыі. [ESLint](https://eslint.org/) — папулярны лінтар з адкрытым зыходным кодам для JavaScript.
+=======
+Code linters find problems in your code as you write, helping you fix them early. [ESLint](https://eslint.org/) is a popular, open source linter for JavaScript.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
* [Усталюйце ESLint з рэкамендаванай канфігурацыяй для React](https://www.npmjs.com/package/eslint-config-react-app) (пераканайцеся, што ў вас усталяваны [Node!](https://nodejs.org/en/download/current/))
* [Інтэгруйце ESLint у VSCode з дапамогай афіцыйнага пашырэння](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)
diff --git a/src/content/learn/escape-hatches.md b/src/content/learn/escape-hatches.md
index ab5f666a..cbaef8bb 100644
--- a/src/content/learn/escape-hatches.md
+++ b/src/content/learn/escape-hatches.md
@@ -227,7 +227,7 @@ function Form() {
}
```
-However, you *do* need Effects to synchronize with external systems.
+However, you *do* need Effects to synchronize with external systems.
@@ -382,7 +382,7 @@ export default function App() {
>
);
@@ -515,7 +515,7 @@ export default function App() {
>
);
diff --git a/src/content/learn/importing-and-exporting-components.md b/src/content/learn/importing-and-exporting-components.md
index 85fd09f6..52414a38 100644
--- a/src/content/learn/importing-and-exporting-components.md
+++ b/src/content/learn/importing-and-exporting-components.md
@@ -28,8 +28,13 @@ title: Імпартаванне і экспартаванне кампанент
function Profile() {
return (
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
);
}
@@ -80,7 +85,7 @@ export default function App() {
function Profile() {
return (
);
@@ -118,7 +123,7 @@ img { margin: 0 10px 10px 0; height: 90px; }
Вы таксама можаце сутыкнуцца з выпадкамі, калі ў назве файла прапушчана частка `.js`:
-```js
+```js
import Gallery from './Gallery';
```
@@ -198,7 +203,7 @@ export default function App() {
export function Profile() {
return (
);
@@ -286,7 +291,7 @@ export default function App() {
export function Profile() {
return (
);
@@ -354,7 +359,7 @@ export default function Gallery() {
export function Profile() {
return (
);
@@ -404,7 +409,7 @@ export default function Gallery() {
export default function Profile() {
return (
);
diff --git a/src/content/learn/index.md b/src/content/learn/index.md
index 160e623c..f4bd82d7 100644
--- a/src/content/learn/index.md
+++ b/src/content/learn/index.md
@@ -143,7 +143,7 @@ return (
```js
const user = {
name: 'Hedy Lamarr',
- imageUrl: 'https://i.imgur.com/yXOvdOSs.jpg',
+ imageUrl: 'https://react.dev/images/docs/scientists/yXOvdOSs.jpg',
imageSize: 90,
};
diff --git a/src/content/learn/javascript-in-jsx-with-curly-braces.md b/src/content/learn/javascript-in-jsx-with-curly-braces.md
index 2aaefe5c..f9b7b92d 100644
--- a/src/content/learn/javascript-in-jsx-with-curly-braces.md
+++ b/src/content/learn/javascript-in-jsx-with-curly-braces.md
@@ -28,8 +28,13 @@ export default function Avatar() {
return (
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
);
}
@@ -41,7 +46,11 @@ export default function Avatar() {
+<<<<<<< HEAD
Тут, `"https://i.imgur.com/7vQD0fPs.jpg"` і `"Грэгорыа І. Зара"` перадаюцца як радкі.
+=======
+Here, `"https://react.dev/images/docs/scientists/7vQD0fPs.jpg"` and `"Gregorio Y. Zara"` are being passed as strings.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
Але што, калі вы хочаце дынамічна задаць значэнне `src` або `alt`? Вы можаце **выкарыстоўваць значэнне з JavaScript, замяніўшы `"` і `"` на `{` і `}`**:
@@ -49,8 +58,13 @@ export default function Avatar() {
```js
export default function Avatar() {
+<<<<<<< HEAD
const avatar = 'https://i.imgur.com/7vQD0fPs.jpg';
const description = 'Грэгорыа І. Зара';
+=======
+ const avatar = 'https://react.dev/images/docs/scientists/7vQD0fPs.jpg';
+ const description = 'Gregorio Y. Zara';
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
return (
Спіс спраў {person.name}
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
Палепшыць відэатэлефон
@@ -266,8 +285,13 @@ export default function TodoList() {
@@ -387,8 +421,13 @@ body > div > div { padding: 20px; }
```js
const person = {
+<<<<<<< HEAD
name: 'Грэгорыа І. Зара',
imageUrl: "https://i.imgur.com/7vQD0fPs.jpg",
+=======
+ name: 'Gregorio Y. Zara',
+ imageUrl: "https://react.dev/images/docs/scientists/7vQD0fPs.jpg",
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
theme: {
backgroundColor: 'black',
color: 'pink'
@@ -428,7 +467,11 @@ body > div > div { padding: 20px; }
У прыведзеным ніжэй аб'екце поўны URL відарыса падзелены на чатыры часткі: базавы URL, `imageId`, `imageSize` і пашырэнне файла.
+<<<<<<< HEAD
Мы хочам аб'яднаць гэтыя атрыбуты разам у URL-адрас відарыса: базавы URL (заўсёды `'https://i.imgur.com/'`), `imageId` (`'7vQD0fP'`), `imageSize` (`'s'`) і пашырэнне файла (заўсёды `'.jpg'`). Аднак нешта не так з тым, як тэг `` вызначае свой `src`.
+=======
+We want the image URL to combine these attributes together: base URL (always `'https://react.dev/images/docs/scientists/'`), `imageId` (`'7vQD0fP'`), `imageSize` (`'s'`), and file extension (always `'.jpg'`). However, something is wrong with how the `` tag specifies its `src`.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
Вы можаце гэта выправіць?
@@ -436,7 +479,7 @@ body > div > div { padding: 20px; }
```js
-const baseUrl = 'https://i.imgur.com/';
+const baseUrl = 'https://react.dev/images/docs/scientists/';
const person = {
name: 'Грэгорыа І. Зара',
imageId: '7vQD0fP',
@@ -487,7 +530,7 @@ body > div > div { padding: 20px; }
```js
-const baseUrl = 'https://i.imgur.com/';
+const baseUrl = 'https://react.dev/images/docs/scientists/';
const person = {
name: 'Грэгорыа І. Зара',
imageId: '7vQD0fP',
@@ -564,7 +607,7 @@ export default function TodoList() {
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
person.imageSize +
'.jpg'
diff --git a/src/content/learn/keeping-components-pure.md b/src/content/learn/keeping-components-pure.md
index 84335f2e..a51d84df 100644
--- a/src/content/learn/keeping-components-pure.md
+++ b/src/content/learn/keeping-components-pure.md
@@ -27,6 +27,7 @@ title: Захоўванне кампанентаў чыстымі
Разгледзім наступную матэматычную формулу: .
+<<<<<<< HEAD
Калі , тады . Заўсёды.
Калі , тады . Заўсёды.
@@ -34,6 +35,15 @@ title: Захоўванне кампанентаў чыстымі
Калі , тады y не будзе часам роўным або , або у залежнасці ад часу сутак або стану фондавага рынку.
Калі і , тады y _заўсёды_ будзе .
+=======
+If then . Always.
+
+If then . Always.
+
+If , y won't sometimes be or or depending on the time of day or the state of the stock market.
+
+If and , y will _always_ be .
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
Калі б мы запісалі гэта як JavaScript функцыю, яна б выглядала наступным чынам:
@@ -52,10 +62,17 @@ React пабудаваны вакол гэтай канцэпцыі. **React м
```js src/App.js
function Recipe({ drinkers }) {
return (
+<<<<<<< HEAD
Закіпяціце {drinkers} шклянкі(-ак) вады.
Дадайце {drinkers} лыжку(-ак) чаю і {0,5 * drinkers} лыжку(-ак) спецый.
Дадайце {0,5 * drinkers} шклянкі(-ак) кіпячонага малака і цукар па гусце.
+=======
+
+
Boil {drinkers} cups of water.
+
Add {drinkers} spoons of tea and {0.5 * drinkers} spoons of spice.
+
Add {0.5 * drinkers} cups of milk to boil and sugar to taste.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
);
}
@@ -75,11 +92,19 @@ export default function App() {
+<<<<<<< HEAD
Калі вы перадаяце `drinkers={2}` у кампанент `Recipe`, ён верне JSX, які змяшчае `2 шклянкі(-ак) вады`. Заўсёды.
+=======
+When you pass `drinkers={2}` to `Recipe`, it will return JSX containing `2 cups of water`. Always.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
Калі вы перадаяце `drinkers={4}` — ён верне JSX, які змяшчае `4 шклянкі(-ак) вады`. Заўсёды.
+<<<<<<< HEAD
Гэтак жа, як матэматычная формула.
+=======
+Just like a math formula.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
Вы можаце разглядаць свой кампанент як рэцэпт: калі яго прытрымлівацца і не ўводзіць новыя інгрэдыенты ў працэсе гатавання, то кожны раз атрымаецца адна і тая ж страва. «Страва» — гэта JSX, які кампанент вяртае React для [рэндэру.](/learn/render-and-commit)
@@ -216,6 +241,7 @@ export default function TeaGathering() {
+<<<<<<< HEAD
* Кампаненты павінны быць чыстымі, што азначае:
* **Займаюцца сваёй справай.** Яны не змяняюць аб’екты або пераменныя, якія існавалі да рэндэрынгу.
* **Вяртаюць прадказальны вынік.** Пры аднолькавых уваходных даных кампанент заўсёды вяртае аднолькавы JSX.
@@ -223,11 +249,20 @@ export default function TeaGathering() {
* Вы не павінны змяняць уваходныя даныя, якія вашы кампаненты выкарыстоўваюць для рэндэрынгу. Гэта могуць быць пропсы, стан або кантэкст. Каб абнавіць экран, [«задайце» (set) стан](/learn/state-a-components-memory) замест таго, каб муціраваць раней існуючыя аб'екты.
* Імкніцеся апісваць логіку вашага кампанента ў JSX, які вы вяртаеце. Калі вам трэба нешта змяніць, лепш гэта зрабіць у апрацоўшчыку падзей. У крайнім выпадку, карыстайцеся `useEffect`.
* Напісанне чыстых функцый патрабуе практыкі, але гэта раскрывае моц парадыгмы React.
+=======
+* A component must be pure, meaning:
+ * **It minds its own business.** It should not change any objects or variables that existed before rendering.
+ * **Same inputs, same output.** Given the same inputs, a component should always return the same JSX.
+* Rendering can happen at any time, so components should not depend on each others' rendering sequence.
+* You should not mutate any of the inputs that your components use for rendering. That includes props, state, and context. To update the screen, ["set" state](/learn/state-a-components-memory) instead of mutating preexisting objects.
+* Strive to express your component's logic in the JSX you return. When you need to "change things", you'll usually want to do it in an event handler. As a last resort, you can `useEffect`.
+* Writing pure functions takes a bit of practice, but it unlocks the power of React's paradigm.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
-
+
#### Выправіць зламаны гадзіннік {/*fix-a-broken-clock*/}
@@ -452,7 +487,7 @@ export default function App() {
```js src/utils.js hidden
export function getImageUrl(person, size = 's') {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
size +
'.jpg'
@@ -550,7 +585,7 @@ export default function App() {
```js src/utils.js hidden
export function getImageUrl(person, size = 's') {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
size +
'.jpg'
diff --git a/src/content/learn/lifecycle-of-reactive-effects.md b/src/content/learn/lifecycle-of-reactive-effects.md
index 72a2e775..608db09a 100644
--- a/src/content/learn/lifecycle-of-reactive-effects.md
+++ b/src/content/learn/lifecycle-of-reactive-effects.md
@@ -293,7 +293,7 @@ You might be wondering how React knew that your Effect needed to re-synchronize
```js {1,3,8}
function ChatRoom({ roomId }) { // The roomId prop may change over time
useEffect(() => {
- const connection = createConnection(serverUrl, roomId); // This Effect reads roomId
+ const connection = createConnection(serverUrl, roomId); // This Effect reads roomId
connection.connect();
return () => {
connection.disconnect();
@@ -969,7 +969,7 @@ export default function App() {
@@ -1027,7 +1027,7 @@ export default function App() {
@@ -1083,7 +1083,7 @@ export default function App() {
@@ -1155,7 +1155,7 @@ export default function App() {
@@ -1220,7 +1220,7 @@ export default function App() {
@@ -1279,7 +1279,7 @@ export default function App() {
@@ -1711,7 +1711,7 @@ async function fetchPlanets() {
name: 'Venus'
}, {
id: 'mars',
- name: 'Mars'
+ name: 'Mars'
}]);
}, 1000);
});
@@ -1735,7 +1735,7 @@ async function fetchPlaces(planetId) {
name: 'Spain'
}, {
id: 'vietnam',
- name: 'Vietnam'
+ name: 'Vietnam'
}]);
} else if (planetId === 'venus') {
resolve([{
@@ -1746,7 +1746,7 @@ async function fetchPlaces(planetId) {
name: 'Diana Chasma'
}, {
id: 'kumsong-vallis',
- name: 'Kŭmsŏng Vallis'
+ name: 'Kŭmsŏng Vallis'
}]);
} else if (planetId === 'mars') {
resolve([{
@@ -1879,7 +1879,7 @@ async function fetchPlanets() {
name: 'Venus'
}, {
id: 'mars',
- name: 'Mars'
+ name: 'Mars'
}]);
}, 1000);
});
@@ -1903,7 +1903,7 @@ async function fetchPlaces(planetId) {
name: 'Spain'
}, {
id: 'vietnam',
- name: 'Vietnam'
+ name: 'Vietnam'
}]);
} else if (planetId === 'venus') {
resolve([{
@@ -1914,7 +1914,7 @@ async function fetchPlaces(planetId) {
name: 'Diana Chasma'
}, {
id: 'kumsong-vallis',
- name: 'Kŭmsŏng Vallis'
+ name: 'Kŭmsŏng Vallis'
}]);
} else if (planetId === 'mars') {
resolve([{
@@ -2042,7 +2042,7 @@ async function fetchPlanets() {
name: 'Venus'
}, {
id: 'mars',
- name: 'Mars'
+ name: 'Mars'
}]);
}, 1000);
});
@@ -2066,7 +2066,7 @@ async function fetchPlaces(planetId) {
name: 'Spain'
}, {
id: 'vietnam',
- name: 'Vietnam'
+ name: 'Vietnam'
}]);
} else if (planetId === 'venus') {
resolve([{
@@ -2077,7 +2077,7 @@ async function fetchPlaces(planetId) {
name: 'Diana Chasma'
}, {
id: 'kumsong-vallis',
- name: 'Kŭmsŏng Vallis'
+ name: 'Kŭmsŏng Vallis'
}]);
} else if (planetId === 'mars') {
resolve([{
diff --git a/src/content/learn/passing-data-deeply-with-context.md b/src/content/learn/passing-data-deeply-with-context.md
index e81678c8..fead4056 100644
--- a/src/content/learn/passing-data-deeply-with-context.md
+++ b/src/content/learn/passing-data-deeply-with-context.md
@@ -857,7 +857,7 @@ If neither of these approaches works well for you, consider context.
* **Current account:** Many components might need to know the currently logged in user. Putting it in context makes it convenient to read it anywhere in the tree. Some apps also let you operate multiple accounts at the same time (e.g. to leave a comment as a different user). In those cases, it can be convenient to wrap a part of the UI into a nested provider with a different current account value.
* **Routing:** Most routing solutions use context internally to hold the current route. This is how every link "knows" whether it's active or not. If you build your own router, you might want to do it too.
* **Managing state:** As your app grows, you might end up with a lot of state closer to the top of your app. Many distant components below may want to change it. It is common to [use a reducer together with context](/learn/scaling-up-with-reducer-and-context) to manage complex state and pass it down to distant components without too much hassle.
-
+
Context is not limited to static values. If you pass a different value on the next render, React will update all the components reading it below! This is why context is often used in combination with state.
In general, if some information is needed by distant components in different parts of the tree, it's a good indication that context will help you.
@@ -963,27 +963,27 @@ export const places = [{
description: 'The tradition of choosing bright colors for houses began in the late 20th century.',
imageId: 'K9HVAGH'
}, {
- id: 1,
+ id: 1,
name: 'Rainbow Village in Taichung, Taiwan',
description: 'To save the houses from demolition, Huang Yung-Fu, a local resident, painted all 1,200 of them in 1924.',
imageId: '9EAYZrt'
}, {
- id: 2,
+ id: 2,
name: 'Macromural de Pachuca, Mexico',
description: 'One of the largest murals in the world covering homes in a hillside neighborhood.',
imageId: 'DgXHVwu'
}, {
- id: 3,
+ id: 3,
name: 'Selarón Staircase in Rio de Janeiro, Brazil',
description: 'This landmark was created by Jorge Selarón, a Chilean-born artist, as a "tribute to the Brazilian people."',
imageId: 'aeO3rpI'
}, {
- id: 4,
+ id: 4,
name: 'Burano, Italy',
description: 'The houses are painted following a specific color system dating back to 16th century.',
imageId: 'kxsph5C'
}, {
- id: 5,
+ id: 5,
name: 'Chefchaouen, Marocco',
description: 'There are a few theories on why the houses are painted blue, including that the color repels mosquitos or that it symbolizes sky and heaven.',
imageId: 'rTqKo46'
@@ -998,7 +998,7 @@ export const places = [{
```js src/utils.js
export function getImageUrl(place) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
place.imageId +
'l.jpg'
);
@@ -1007,9 +1007,9 @@ export function getImageUrl(place) {
```css
ul { list-style-type: none; padding: 0px 10px; }
-li {
- margin-bottom: 10px;
- display: grid;
+li {
+ margin-bottom: 10px;
+ display: grid;
grid-template-columns: auto 1fr;
gap: 20px;
align-items: center;
@@ -1102,27 +1102,27 @@ export const places = [{
description: 'The tradition of choosing bright colors for houses began in the late 20th century.',
imageId: 'K9HVAGH'
}, {
- id: 1,
+ id: 1,
name: 'Rainbow Village in Taichung, Taiwan',
description: 'To save the houses from demolition, Huang Yung-Fu, a local resident, painted all 1,200 of them in 1924.',
imageId: '9EAYZrt'
}, {
- id: 2,
+ id: 2,
name: 'Macromural de Pachuca, Mexico',
description: 'One of the largest murals in the world covering homes in a hillside neighborhood.',
imageId: 'DgXHVwu'
}, {
- id: 3,
+ id: 3,
name: 'Selarón Staircase in Rio de Janeiro, Brazil',
description: 'This landmark was created by Jorge Selarón, a Chilean-born artist, as a "tribute to the Brazilian people".',
imageId: 'aeO3rpI'
}, {
- id: 4,
+ id: 4,
name: 'Burano, Italy',
description: 'The houses are painted following a specific color system dating back to 16th century.',
imageId: 'kxsph5C'
}, {
- id: 5,
+ id: 5,
name: 'Chefchaouen, Marocco',
description: 'There are a few theories on why the houses are painted blue, including that the color repels mosquitos or that it symbolizes sky and heaven.',
imageId: 'rTqKo46'
@@ -1137,7 +1137,7 @@ export const places = [{
```js src/utils.js
export function getImageUrl(place) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
place.imageId +
'l.jpg'
);
@@ -1146,9 +1146,9 @@ export function getImageUrl(place) {
```css
ul { list-style-type: none; padding: 0px 10px; }
-li {
- margin-bottom: 10px;
- display: grid;
+li {
+ margin-bottom: 10px;
+ display: grid;
grid-template-columns: auto 1fr;
gap: 20px;
align-items: center;
diff --git a/src/content/learn/passing-props-to-a-component.md b/src/content/learn/passing-props-to-a-component.md
index a8ed47e0..6ca4bf75 100644
--- a/src/content/learn/passing-props-to-a-component.md
+++ b/src/content/learn/passing-props-to-a-component.md
@@ -29,8 +29,13 @@ function Avatar() {
return (
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
width={100}
height={100}
/>
@@ -126,22 +131,36 @@ export default function Profile() {
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
width={100}
height={100}
/>
@@ -1073,8 +1155,13 @@ export default function Profile() {
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
width={100}
height={100}
/>
diff --git a/src/content/learn/preserving-and-resetting-state.md b/src/content/learn/preserving-and-resetting-state.md
index 041fae35..685f63ef 100644
--- a/src/content/learn/preserving-and-resetting-state.md
+++ b/src/content/learn/preserving-and-resetting-state.md
@@ -86,7 +86,7 @@ label {
-Here's how these look as a tree:
+Here's how these look as a tree:
@@ -186,7 +186,7 @@ export default function App() {
return (
- {showB && }
+ {showB && }
);
@@ -594,7 +594,7 @@ export default function Picture() {
}}
className={pictureClassName}
alt="Rainbow houses in Kampung Pelangi, Indonesia"
- src="https://i.imgur.com/5qwVYb1.jpeg"
+ src="https://react.dev/images/docs/scientists/5qwVYb1.jpeg"
/>
);
@@ -649,7 +649,7 @@ export default function Picture() {
e.stopPropagation()}
/>
@@ -660,7 +660,7 @@ export default function Picture() {
setIsActive(true)}
/>
diff --git a/src/content/learn/referencing-values-with-refs.md b/src/content/learn/referencing-values-with-refs.md
index 4386e2bd..657d3ddc 100644
--- a/src/content/learn/referencing-values-with-refs.md
+++ b/src/content/learn/referencing-values-with-refs.md
@@ -34,7 +34,7 @@ const ref = useRef(0);
`useRef` returns an object like this:
```js
-{
+{
current: 0 // The value you passed to useRef
}
```
diff --git a/src/content/learn/removing-effect-dependencies.md b/src/content/learn/removing-effect-dependencies.md
index 61eb2e8d..0b69cfa6 100644
--- a/src/content/learn/removing-effect-dependencies.md
+++ b/src/content/learn/removing-effect-dependencies.md
@@ -411,7 +411,7 @@ function Form() {
function handleSubmit() {
setSubmitted(true);
- }
+ }
// ...
}
@@ -429,7 +429,7 @@ function Form() {
// ✅ Good: Event-specific logic is called from event handlers
post('/api/register');
showNotification('Successfully registered!', theme);
- }
+ }
// ...
}
@@ -878,7 +878,7 @@ const options2 = { serverUrl: 'https://localhost:1234', roomId: 'music' };
console.log(Object.is(options1, options2)); // false
```
-**Object and function dependencies can make your Effect re-synchronize more often than you need.**
+**Object and function dependencies can make your Effect re-synchronize more often than you need.**
This is why, whenever possible, you should try to avoid objects and functions as your Effect's dependencies. Instead, try moving them outside the component, inside the Effect, or extracting primitive values out of them.
diff --git a/src/content/learn/render-and-commit.md b/src/content/learn/render-and-commit.md
index 6d6d70df..2552f151 100644
--- a/src/content/learn/render-and-commit.md
+++ b/src/content/learn/render-and-commit.md
@@ -53,8 +53,13 @@ root.render();
export default function Image() {
return (
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
);
}
@@ -102,8 +107,13 @@ export default function Gallery() {
function Image() {
return (
>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
/>
);
}
@@ -123,8 +133,13 @@ img { margin: 0 10px 10px 0; }
+<<<<<<< HEAD
- **Пры першапачатковым рэндэры** React [створыць DOM-вузлы](https://developer.mozilla.org/docs/Web/API/Document/createElement) для ``, `
` і трох `` тэгаў.
- **Падчас паўторнага рэндэру** React падлічыць, якія з іх уласцівасцей, калі такія маюцца, змяніліся з моманту папярэдняга рэндэру. Ён нічога не будзе рабіць з гэтай інфармацыяй да наступнага кроку, фазы фіксацыі.
+=======
+* **During the initial render,** React will [create the DOM nodes](https://developer.mozilla.org/docs/Web/API/Document/createElement) for ``, `
`, and three `` tags.
+* **During a re-render,** React will calculate which of their properties, if any, have changed since the previous render. It won't do anything with that information until the next step, the commit phase.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
diff --git a/src/content/learn/rendering-lists.md b/src/content/learn/rendering-lists.md
index 3002e85b..618cad42 100644
--- a/src/content/learn/rendering-lists.md
+++ b/src/content/learn/rendering-lists.md
@@ -114,8 +114,13 @@ const people = [{
profession: 'фізік',
}, {
id: 3,
+<<<<<<< HEAD
name: 'Персі Лавон Джуліан',
profession: 'хімік',
+=======
+ name: 'Percy Lavon Julian',
+ profession: 'chemist',
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
}, {
id: 4,
name: 'Субрахманьян Чандрасекар',
@@ -223,7 +228,7 @@ export const people = [{
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
's.jpg'
);
@@ -232,9 +237,9 @@ export function getImageUrl(person) {
```css
ul { list-style-type: none; padding: 0px 10px; }
-li {
- margin-bottom: 10px;
- display: grid;
+li {
+ margin-bottom: 10px;
+ display: grid;
grid-template-columns: auto 1fr;
gap: 20px;
align-items: center;
@@ -353,7 +358,7 @@ export const people = [{
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
's.jpg'
);
@@ -362,9 +367,9 @@ export function getImageUrl(person) {
```css
ul { list-style-type: none; padding: 0px 10px; }
-li {
- margin-bottom: 10px;
- display: grid;
+li {
+ margin-bottom: 10px;
+ display: grid;
grid-template-columns: auto 1fr;
gap: 20px;
align-items: center;
@@ -514,7 +519,7 @@ export const people = [{
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
's.jpg'
);
@@ -629,7 +634,7 @@ export const people = [{
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
's.jpg'
);
@@ -743,7 +748,7 @@ export const people = [{
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
's.jpg'
);
@@ -861,7 +866,7 @@ export const people = [{
```js src/utils.js
export function getImageUrl(person) {
return (
- 'https://i.imgur.com/' +
+ 'https://react.dev/images/docs/scientists/' +
person.imageId +
's.jpg'
);
diff --git a/src/content/learn/responding-to-events.md b/src/content/learn/responding-to-events.md
index 4e558118..c29cd005 100644
--- a/src/content/learn/responding-to-events.md
+++ b/src/content/learn/responding-to-events.md
@@ -168,7 +168,11 @@ button { margin-right: 10px; }
### Перадача апрацоўшчыкаў падзей у якасці пропсаў {/*passing-event-handlers-as-props*/}
+<<<<<<< HEAD
Часта вам можа спатрэбіцца, каб бацькоўскі кампанент вызначаў апрацоўшчыка падзей для даччынага кампанента. Разгледзім кнопкі: у залежнасці ад таго, дзе вы выкарыстоўваеце кампанент `Button`, вам можа спатрэбіцца выконваць розныя функцыі — магчыма, адна кнопка павінна прайграваць фільм, а другая загружаць відарыс.
+=======
+Often you'll want the parent component to specify a child's event handler. Consider buttons: depending on where you're using a `Button` component, you might want to execute a different function—perhaps one plays a movie and another uploads an image.
+>>>>>>> abe931a8cb3aee3e8b15ef7e187214789164162a
Каб зрабіць гэта, перадайце кампаненту пропс, які ён атрымлівае ад свайго бацькі, у якасці апрацоўшчыка падзей, наступным чынам:
@@ -311,12 +315,21 @@ button { margin-right: 10px; }
+<<<<<<< HEAD
Звярніце ўвагу, што кампанент `App` не павінен ведаць, *што* кампанент `Toolbar` будзе рабіць з `onPlayMovie` або `onUploadImage`. Гэта дэталі рэалізацыі `Toolbar`. У гэтым прыкладзе `Toolbar` перадае іх у якасці апрацоўшчыкаў падзеі `onClick` сваім кампанентам `Button`, але пазней ён таксама можа выклікаць іх па спалучэнні клавіш. Называнне пропсаў у адпаведнасці са спецыфікай вашай праграмы, напрыклад `onPlayMovie`, дае вам магчымасць змяніць спосаб іх выкарыстання ў будучыні.
Упэўніцеся, што вы выкарыстоўваеце адпаведныя HTML тэгі для апрацоўшчыкаў падзей. Напрыклад, для апрацоўкі націскання выкарыстоўвайце [`