Skip to content
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

Next 15 displays empty error on dev overlay #524

Closed
domosedov opened this issue Oct 26, 2024 · 6 comments
Closed

Next 15 displays empty error on dev overlay #524

domosedov opened this issue Oct 26, 2024 · 6 comments

Comments

@domosedov
Copy link

Describe the bug
Example from docs

Empty error message in Next.js error overlay with Next 15/React 19 deps
Снимок экрана 2024-10-27 в 00 05 37

https://stackblitz.com/edit/stackblitz-starters-rv8vkm

@inokawa
Copy link
Owner

inokawa commented Oct 27, 2024

The error seems to be the same as #470 (it's not visible in Chrome by default. BTW Next.js should show it even so).

The error itself is safe so you can ignore it. However Next.js doesn't seem to have a way to ignore certain errors like Webpack...
vercel/next.js#13387
vercel/next.js#23970

@inokawa inokawa changed the title Next 15/React 19 Support Next 15 displays empty error overlay Oct 27, 2024
@inokawa inokawa changed the title Next 15 displays empty error overlay Next 15 displays empty error on dev overlay Oct 27, 2024
@fernandops26
Copy link

any update here?

@t3dotgg
Copy link

t3dotgg commented Jan 18, 2025

+1 on this, really annoying in dev (love the library but the error comes up super randomly when working on T3 Chat)

@alexomon018
Copy link

+1 on this too, as I have been also working on chat app.

@t3dotgg
Copy link

t3dotgg commented Feb 14, 2025

Two things:

  1. The issue as described (Next.js showing an error that doesn't appear in Chrome console) has been fixed by the Next.js team as of 15.1.6: Fix presentation when onerror receives an event without error vercel/next.js#74643

  2. I still see the errors a lot, but they also appear in the Chrome console

Image

I was able to suppress the errors I got on page load by avoiding rendering the vlist until I had children to render in it. Sadly, when I scroll the errors still come back

Technically, I think this issue is "fixed" and a separate one might be necessary for the additional errors I am seeing. lmk what's best @inokawa

@inokawa
Copy link
Owner

inokawa commented Feb 14, 2025

Thanks for the information. So I close this issue.

And I reopened #470 to seek possible solution and discuss further.

@inokawa inokawa closed this as completed Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants