-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Suspense: DOMException: Failed to execute 'insertBefore' on 'Node' #3105
Comments
I have the same problem, just tried Preact for the first time, and I get this error anytime I start my app... Unfortunately, the softfix does not work for me, so I just can't use Preact until it's fixed. |
This issue seems fixed with Preact 10.8.2 https://codesandbox.io/s/misty-cloud-u5et4t, closing for now but feel free to reopen if the issue persists for you. |
Hey there! The issue appeared with Preact 10.11.2 |
Hello ! I'm still having this problem with If it can help, I was playing with each release and it seems that everything is working fine with the So technically something related with the |
As a possible fix to already compiled bundle, the following can be used: webpackConfig.module.rules.push({
test: new RegExp('preact/compat'),
loader: require.resolve('./preact-patch'),
}); And the loader contents:
But indeed, why is not the |
Hello, I am also getting this error, is there a fix or can we reopen this issue? |
Hi, Seems the issue occures in the latest version aswell. can anyone share the solution/fix for this. |
Hi, I'm having the same error from the latest version, whats the way forward please? |
This solved it for my particular case :) |
Describe the bug
If there are multiple components that suspended at the same time and tried to resolve at the same time, there's a chance that only one of the components will successfully re-render while the rest stays in their fallback state. I'm not sure the specificity but I think one of the reasons is that Preact fails to match the component vdom to the actual dom node.
Once it fails to resolve, it throws this error:
This may also happen if one of the components, that isn't suspending, updates during the resolution timeframe.
A softfix for this is to wrap Suspending components with a container like a simple
<div>
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should've been able to continuously retain the same behavior prior to the error.
The text was updated successfully, but these errors were encountered: