Replies: 1 comment
-
This is just Sentry being an absolute nightmare. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Basically, every single non-page "route" handler (that is, api route in app router - these labels make it impossible...) stopped"generating" in my very large app. The error I get is completely incomprehensible, pointing to some chunk line-of-code, in the compiled state. Utterly useless. I can work around this by making my routes dynamic, and eating the performance hit - that seems right. Likely, no one at Vercel gives a crap, since this is using a regular app build, not meant for Vercel or OpenNext.
Anyway - anyone else seeing this type of error? I'm using Sentry, which I suspect has something to do with this (it's mandated, I wouldn't recommend using that thing with next.js.)
Additional information
I'm using next build --experimental-build-mode compile and generate - the errors happen in the generate step. Yes, somehow, after a couple of years, this is still experimental...
Update: Yeah, it was Sentry. I disabled that, and it all started working....
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions