Skip to content

Commit 6f645cf

Browse files
committed
Add more StrictMode notes
1 parent 24323ca commit 6f645cf

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

doc/ReactFeatures.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -335,14 +335,16 @@ See [Security](./Security.md)
335335

336336
## [StrictMode](https://react.dev/reference/react/StrictMode)
337337

338-
(React 19)
338+
(React 18/19 Concurrent Mode, i.e. createRoot)
339339

340340
React StrictMode should help with finding bugs in your React components. With
341341
Reagent this unfortunately might not be helpful.
342342

343343
> Your components will re-render an extra time to find bugs caused by impure rendering.
344344
> [Fixing bugs found by double rendering in development ](https://react.dev/reference/react/StrictMode#fixing-bugs-found-by-double-rendering-in-development)
345345
346+
[React v18, New Strict Mode Behaviors](https://react.dev/blog/2022/03/29/react-v18#new-strict-mode-behaviors)
347+
346348
In Reagent, triggering a side-effects from render functions has been somewhat
347349
common use, though it is not recommended in React. The Reagent demo site timer-component
348350
for example uses `js/setTimeout` directly in the render function to trigger

0 commit comments

Comments
 (0)