-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Application Error: failed to execute insertBefore on Node #9242
Comments
Would you mind putting together a small stackblitz via https://remix.new to demonstrate the issue? |
I would like to, but my Remix App, have too many codes, and I don't know how to put everything there on stackblitz. |
How are we supposed to reproduce and triage your issue if we don't know how it's setup? Usually when folks begin to remove aspects one by one in order to get down to a simplified reproduction - they end up identifying the problem on their own. I would suggest doing that locally - identify a singular route that exhibits the problem, and then begin removing aspects (components, styles, etc.). Eventually you'll either see the problem disappear and know that the last thing you removed was the problem - or you'll end up with nothing left to remove and that can be used as your minimal reproduction. |
|
Sorry for the problem in previous link |
That doesn't run for me either unfortunately: It looks like that's just pulling from a cloned github repo with your entire app in it - which doesn't really help us narrow down the problem. It would be really helpful if you could remove extraneous stuff to narrow down to the root cause and provide a minimal reproduction. Like I said - 90% of the time that process will uncover the root cause and it will be related to a third party or an extension or something else unique to your application. If it does end up being a problem in core Remix then the minimal reproduction makes it significantly easier for us to triage. That said, when I pull your repo neither |
@brophdawg11 is there any way to catch errors? like the error I mentioned, for that to catch like from where this is error is happening? any idea? |
Furthermore, I tried to debug in my local again, where I disabled all my Chrome Plugins, and tried but still the issue is still there.. Also, I am using a Remix DevTools Plugin, so I tried to remove it and tried but the issue is still there. screen-capture.webmHere is the recording of the issue, I am still encountering... |
Furthermore @brophdawg11 I tried to remove 2 of my Tailwind Library, 1 is I am using Incognito Mode only, but still I am encountering the issue. sometimes only by Navigating from one to another or sometime if I am modifying in As I mentioned in previous comment, I disabled all the Chrome Extensions and then tried but the error remains there. |
I am getting error in such like, go to About Us Page, wait for 2 seconds, modify something in the code, save and the HMR will happen and then go to top and click on |
Same error here. I'm using the Here is a traceback:
It appears randomly in dev mode. Probably just a race condition somewhere. If I refresh it works. |
Happens to me as well, and with a brand new |
I can still reproduce the bug consistently. Give this repro repo a shot: https://github.com/ironbyte/remix-run-issue-9242-repro issue_9242_repro_video_clip.webmFAQs:
|
FYI when downloading @ironbyte 's github repo which has these remix package versions in its package.json file
you'll want to remove the since this reproduction was created before the 2.9.0 release, I'm assuming 2.8.1 is the version that ironbyte used and ran into issues with |
Updated the repro repo (Pin Remix versions to 2.8.1) - ironbyte/remix-run-issue-9242-repro@960fd8d BTW, the issue still persists after upgrading Remix deps to 2.9.0 on a separate branch ( |
possibly related to - #9276 |
It seems that the bug is triggered when navigating back to the index route in any way (using |
Same here, any progress on the topic? remix packages @2.9.1 I can confirm that I can reproduce the behaviour as described above:
Works in both directions.
|
I am getting this error as well. It started after I added the meta function to a route. If I comment out the meta function, this error goes away.
|
@jdgamble555 unfortunately that didn't fix the issue. It seems to only happen on less often though.. |
i'm encountering the same issue. Same consistent way of reproducing the error. I do have the rollup override
Any other info that i can provide that might be of help, please let me know. |
I could not find a 100% reproducible example, but I also noted the same error quite often. It seems it only happens navigating to |
I started getting these errors randomly when I introduced |
I am still experiencing the above-mentioned problem even till today with the latest version of Now I am getting this error is like, in when we can expect the permanent fix for this issue? |
Same issue here with @ClimenteA . I don't know if this affect the production though? Sometime it appear on dev mode. |
No issues in prod. Just on dev it appears sometimes. |
Thanks for confirming. |
I have also reproduced as same way. And I found that , the problem had happened after I wrote 'MetaFunction()' every Page. |
Possibly related? facebook/react#11538 (comment) |
Same issue when using
|
I am still encountering the same issue. |
Still encountering this issue. |
Still seeing this issue with Rollup 4.20.0 |
any progress on this? i tired the workarounds locked rollup version, and also tried upgrading vite and remix to the latest versions and this issue is still happening. |
I was able to look into this a little bit this AM and simplified @ironbyte's repo down to a minimal reproduction and the issue is not just triggering HMR but specifically triggering Vite's CSS HMR and then navigating back. The issue only occurs after you see https://github.com/brophdawg11/remix-run-issue-9242-repro That console line comes from this line in the vite code which is responsible for doing CSS HMR. I'm curious if anyone has found anything in vite's issue similar to this? It feels like it has something do to with how vite swaps the element for CSS HMR instead of changing the href (which is useful to prevent FOUC as stated in the code comment). But maybe that approach is at odds with reacts dom diffing/reconciliation algorithm? My hunch is that this is potentially something that could be reproduced outside of a Remix context but I don't have the time to prove that out at the moment. |
Reproduction
this is my
package.json
this is my
vite.config.ts
System Info
Used Package Manager
npm
Expected Behavior
no error of
insertBefore
on Node error should occurActual Behavior
and below is my
root.tsx
:import type { LinksFunction } from '@remix-run/node'
import { Links, Meta, Outlet, Scripts, ScrollRestoration } from '@remix-run/react'
// Stylesheet
import tailwindCss from '~/styles/tailwind.css?url'
// Layout
import CustomLayout from './layout'
// Preline Init
import { PrelineInitScript } from './components/custom-scripts'
// Constants
import { APP_NAME } from './constants'
export const links: LinksFunction = () => {
return [{ rel: 'stylesheet', href: tailwindCss }]
}
export default function App() {
return (
)
}
The text was updated successfully, but these errors were encountered: