-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Error handling fixes for turbopack-node
and the HMR runtime
#5189
Error handling fixes for turbopack-node
and the HMR runtime
#5189
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
9 Ignored Deployments
|
turbopack-node
and the HMR runtime
✅ This change can build |
|
Linux Benchmark for 66ee3eaClick to view benchmark
|
7660790
to
cdadd15
Compare
Linux Benchmark for 61e7da1
Click to view full benchmark
|
1d73fd2
to
dfd440d
Compare
Linux Benchmark for 8806d6cClick to view benchmark
|
crates/turbopack-ecmascript-runtime/js/src/dev/runtime/base/runtime-base.ts
Outdated
Show resolved
Hide resolved
@@ -133,9 +136,11 @@ function createIpc<TIncoming, TOutgoing>( | |||
...structuredError(error), | |||
}); | |||
} catch (err) { | |||
console.error("failed to send error back to rust:", err); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should only be logged in some kind of verbose/tracing mode, as I don't think it's very actionable from a user's perspective.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added this because previously the error outputted was something like "unexpected EOF" so while it might not be actionable I thought it might be easier to understand and if we receive feedback easier to debug, can remove it again though
dfd440d
to
516a886
Compare
823e706
to
e637d54
Compare
Linux Benchmark for 6a402afClick to view benchmark
|
e637d54
to
30aa8da
Compare
Linux Benchmark for de987a9
Click to view full benchmark
|
Windows Benchmark for de987a9
Click to view full benchmark
|
### Turbopack Updates * vercel/turborepo#5156 * vercel/turborepo#5159 * vercel/turborepo#5162 * vercel/turborepo#5161 * vercel/turborepo#5174 * vercel/turborepo#5178 * vercel/turborepo#5121 * vercel/turborepo#5200 * vercel/turborepo#5207 * vercel/turborepo#5211 * vercel/turborepo#5210 * vercel/turborepo#5221 * vercel/turborepo#5218 * vercel/turborepo#5226 * vercel/turborepo#5139 * vercel/turborepo#5227 * vercel/turborepo#5189
### Turbopack Updates * vercel/turborepo#5156 * vercel/turborepo#5159 * vercel/turborepo#5162 * vercel/turborepo#5161 * vercel/turborepo#5174 * vercel/turborepo#5178 * vercel/turborepo#5121 * vercel/turborepo#5200 * vercel/turborepo#5207 * vercel/turborepo#5211 * vercel/turborepo#5210 * vercel/turborepo#5221 * vercel/turborepo#5218 * vercel/turborepo#5226 * vercel/turborepo#5139 * vercel/turborepo#5227 * vercel/turborepo#5189
…/turborepo#5189) ### Description - errors during module init are no longer ignored - non-Errors thrown inside node.js now display correctly Bonus: - you can now debug the spawned node.js processes without recompiling via `TURBOPACK_DEBUG_JS=operation`
…/turborepo#5189) ### Description - errors during module init are no longer ignored - non-Errors thrown inside node.js now display correctly Bonus: - you can now debug the spawned node.js processes without recompiling via `TURBOPACK_DEBUG_JS=operation`
…/turborepo#5189) ### Description - errors during module init are no longer ignored - non-Errors thrown inside node.js now display correctly Bonus: - you can now debug the spawned node.js processes without recompiling via `TURBOPACK_DEBUG_JS=operation`
Description
Bonus:
TURBOPACK_DEBUG_JS=operation
Fixes WEB-997