Comments (5)
Hi @catamphetamine ,
You're using strict mode, and useInsertionEffect
does not mount twice the way useLayoutEffect
and useEffect
do.
from react.
You're using strict mode, and
useInsertionEffect
does not mount twice the wayuseLayoutEffect
anduseEffect
do.
Thanks, but why doesn't it though?
Don't you consider it a bug?
They're all "effect"s, so why does their behavior differ in strict mode?
That makes no sense and useInsertionEffect()
isn't supposed to be anything "special":
useInsertionEffect
is a version of useEffect that fires before any DOM mutations.
From the official docs:
https://beta.reactjs.org/reference/react/useInsertionEffect
So I consider the current behavior a bug.
from react.
Looks like in the current versions of React, the only workaround for the "strict" mode would be modifying the effect hooks like this:
import { useRef, useCallback } from 'react'
// A workaround for a React bug when `useInsertionEffect()` doesn't run twice on mount
// in "strict" mode unlike `useEffect()` and `useLayoutEffect()` do.
// https://github.com/facebook/react/issues/26320
export default function useEffectDontMountTwiceInStrictMode(useEffect, handler, dependencies) {
if (!Array.isArray(dependencies)) {
throw new Error('Dependencies argument must be an array')
}
const { onEffect } = useEffectStatus()
const { onChange } = usePrevousValue(dependencies)
useEffect(() => {
const { isInitialRun } = onEffect()
const previousDependencies = onChange(dependencies)
if (isInitialRun || !isShallowEqualArrays(previousDependencies, dependencies)) {
const cleanUpFunction = handler()
if (typeof cleanUpFunction === 'function') {
throw new Error('An effect can\'t return a clean-up function when used with `useEffectDontMountTwiceInStrictMode()` because the clean-up function won\'t behave correctly in that case')
}
}
}, dependencies)
}
function useEffectStatus() {
const hasMounted = useRef(false)
const onEffect = useCallback(() => {
const wasAlreadyMounted = hasMounted.current
hasMounted.current = true
return {
isInitialRun: !wasAlreadyMounted
}
}, [])
return {
onEffect
}
}
function usePrevousValue(value) {
const prevValue = useRef(value)
const onChange = useCallback((value) => {
const previousValue = prevValue.current
prevValue.current = value
return previousValue
}, [])
return {
onChange
}
}
function isShallowEqualArrays(a, b) {
if (a.length !== b.length) {
return false
}
let i = 0
while (i < a.length) {
if (a[i] !== b[i]) {
return false
}
i++
}
return true
}
import { useLayoutEffect } from 'react'
function Component() {
useEffectDontMountTwiceInStrictMode(useLayoutEffect, handler, dependencies)
}
For example, in my case, a library uses useInsertionEffect()
/ useLayoutEffect()
to squeeze into that tiny timeframe in order to accept some calls from child components' useLayoutEffect()
s, so 1:1
calls correspondence is a requirement.
from react.
I think you are correct, it needs to mount twice. I am working on this bug now and the discussion is happening here #26332
from react.
@egonSchiele Wow, that was quick, thanks
from react.
Related Issues (20)
- Bug: Auto-inserted `rel=preload` script resources are blocked by nonce-CSP HOT 5
- React Component not rendering HOT 10
- Bug: I dunno whether its a bug or a default feature of React, under Sources tab of chrome dev tools, complete source code of my frontend project is getting exposed whether I run it locally or in production. I researched on this and tried many methods but it's still visible. HOT 4
- [DevTools Bug] Cannot add node "1751" because a node with that id is already in the Store. HOT 10
- [DevTools Bug] Cannot remove node "226752" because no matching node was found in the Store. HOT 11
- [DevTools Bug]: Regression - profiling doesn't store props value HOT 1
- [DevTools Bug]: Using different React instances across multiple frames throws errors HOT 4
- Bug:
- Props passed to components in an array are never updated HOT 6
- Bug: Don't crash the app if an async component is accidentally used on the client HOT 1
- Bug:
- Bug: Unable to type new character when textarea is focused, happen when using Japanese IME on IOS HOT 4
- Built-in Form Handling HOT 2
- Bug: Auto generated preload links should respect fetchpriority if specified HOT 5
- Bug: useTransition and uSES do not work together, uT is not resilient to amount-of-render HOT 1
- Bug: Dialog issue - Multiple modals appearing and close button not working HOT 1
- Bug: React 18 upgrade getting uncaught runtime errors HOT 2
- [DevTools Bug]: Strict mode badge points to the old docs HOT 4
- Update copyright text to Meta instead of Facebook HOT 5
- Bug: Cannot read properties of null (reading 'useState') HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from react.