-
Notifications
You must be signed in to change notification settings - Fork 0
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
NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. #1797
Comments
function uH(e, n, t) {
if (e6 && "function" == typeof e6.onCommitFiberUnmount)
try {
e6.onCommitFiberUnmount(e5, t)
} catch (e) {}
switch (t.tag) {
case 5:
uT || uM(t, n);
case 6:
var r = uA
, l = uj;
uA = null,
uB(e, n, t),
uA = r,
uj = l,
null !== uA && (uj ? (e = uA,
t = t.stateNode,
8 === e.nodeType ? e.parentNode.removeChild(t) : e.removeChild(t)) : uA.removeChild(t.stateNode)); // last removeChild is where the error is happening
break;
case 18:
null !== uA && (uj ? (e = uA,
t = t.stateNode,
8 === e.nodeType ? r_(e.parentNode, t) : 1 === e.nodeType && r_(e, t),
nM(e)) : r_(uA, t.stateNode));
break;
case 4:
r = uA,
l = uj,
uA = t.stateNode.containerInfo,
uj = !0,
uB(e, n, t),
uA = r,
uj = l;
break;
case 0:
case 11:
case 14:
case 15:
if (!uT && null !== (r = t.updateQueue) && null !== (r = r.lastEffect)) {
l = r = r.next;
do {
var a = l
, u = a.destroy;
a = a.tag,
void 0 !== u && (0 != (2 & a) ? uF(t, n, u) : 0 != (4 & a) && uF(t, n, u)),
l = l.next
} while (l !== r)
}
uB(e, n, t);
break;
case 1:
if (!uT && (uM(t, n),
"function" == typeof (r = t.stateNode).componentWillUnmount))
try {
r.props = t.memoizedProps,
r.state = t.memoizedState,
r.componentWillUnmount()
} catch (e) {
o$(t, n, e)
}
uB(e, n, t);
break;
case 21:
default:
uB(e, n, t);
break;
case 22:
1 & t.mode ? (uT = (r = uT) || null !== t.memoizedState,
uB(e, n, t),
uT = r) : uB(e, n, t)
}
} |
also timing of these showing up seems to coincide with #1726 |
it seems like this has been solved via the swcMinify pull #1846 |
Great, let's keep an eye on this though. |
Even after a while this is still not showing out anymore. |
This small change took some digging. 1) We decided to try setting this to false in hopes of fixing two issues #1797 #1846 The first issue was fixed (1797) while the second issue was not (1846). 2) Next 14 fails to build with terser enabled. This is because terser doesn't support node some out the new tsx used by Next 14. The error is: ../pages/_document.js from Terser Unexpected token: punc ({) [../pages/_document.js:675,10] My best guess from some googling is this is due to the class static keyword: terser/terser#1160 However, this is fixed simply by using the SWC minifier (default) instead of terser. 3) Now with Next 14 the docs claim we shouldn't need terser anymore: https://nextjs.org/docs/architecture/nextjs-compiler In fact, Terser will not be supported in Next 15 slated for release next year.
Sentry Issue: REACT-COMMERCE-2EV
The text was updated successfully, but these errors were encountered: