Error messages do not tell me where they are coming from with Turbopack, Next 15.2.0
Unanswered
MaKTaiL posted this in #help-forum
MaKTaiLOP
I took two screenshots of an error test on both Turbopack and No Turbopack runs. Is this normal behavior?
11 Replies
MaKTaiLOP
Anyone??
@MaKTaiL I took two screenshots of an error test on both Turbopack and No Turbopack runs. Is this normal behavior?
American Foxhound
The difference you might observe could be in how the errors are displayed or logged, but the core behavior remains the same.
@American Foxhound The difference you might observe could be in how the errors are displayed or logged, but the core behavior remains the same.
MaKTaiLOP
That's obvious. What I asked is EXACTLY why they look different.
@MaKTaiL That's obvious. What I asked is EXACTLY why they look different.
American Foxhound
That's becuase of Turbopack
@American Foxhound That's becuase of Turbopack
MaKTaiLOP
Again, I'm aware. You still haven't answered my original question.
American Foxhound
Firstone is bundled directory
@MaKTaiL That's obvious. What I asked is EXACTLY why they look different.
Probably a bug lol, I've seen people in other threads reporting the same issue and none has got a real answer yet.
Let's hope it gets fixed or someone comes with a solution
Let's hope it gets fixed or someone comes with a solution
@MaKTaiL Thanks. Does this happen with you?
Not that one exactly, maybe Turbopack isn’t fully ready for development like they claim xd
when I get weird errors like those I delete my .next folder and node_modules and sometimes that fixes it.
when I get weird errors like those I delete my .next folder and node_modules and sometimes that fixes it.
that is the reason why turbopack can't trace back the source of the error