Jacob Smith

@bmeck @MylesBorins could either of you speak to the impetus for this?

Since Node.js doesn't maintain anything of the sort, that sounds like a better alternative to "surprise!". It's not full-proof, though.

We have a working Proof of Concept: https://github.com/JakobJingleheimer/worker-atomics

> Hi! Any estimated date for done this thread ? > > This thread blocking #43772 which needed for > > [https://github.com/yarnpkg/berry/discussions/4044#discussioncomment-2740697](url) > > Asking cause looks like it's long...

I was chatting with Anna earlier today, and she mentioned the CPU and memory cost of the 2nd thread is non-trivial—effectively doubling node's basic footprint. Is that something we've already...

**Edit**: I believe it was always our intention to get those numbers before landing. --- > 1. how much more memory is needed? This does not seem to be a...

> A few more question: > 1. if a new Worker thread is spawned in the lifetime of the application, will this create another thread to load ESM? > 2....

Sorry, I think https://github.com/nodejs/node/issues/43658#issuecomment-1288637199 is the intended behaviour (the current PR may not achieve that yet). The rationale being that workers are intended to be isolated, so their loaders' state...

A recent change (#42314) converted some of ESMLoader's experimental warning emissions from using `process.emitWarning()` directly to an internal utility ([`emitExperimentalWarning()`](https://github.com/nodejs/node/blob/master/lib/internal/util.js#L219-L225)) that uses it under the hood. Since it still uses...

Could you cite a problematic place where that happens? A quick search of the node codebase suggests it's used only sparingly and in very specific scenarios. `process.emitWarning` does call `process.emit()`:...