Bradley Farias

Just stating I'd love to have this around, I'm looking into message busses for Node and having `.wait` be blocking means scaling up Worker counts to :( levels.

Path to Stage 3

10

- [x] Complete Spec Text - [ ] Reviewers - [ ] TBD - [ ] TBD - [ ] Editor Sign Off Note: Removing *Set due to indefinite bike...

rename hooks

14

The names `toKey` / `toValue` might be confusing if we ad an identity/equality hook in the future. Calling these `coerceKey` and `coerceValue` likely is acceptable.

`import *` potentially doesn't need to parse/link

3

Given that there is no linkage required required for `import *` likely it can avoid parsing or linkage if cycles are not present in some way. The only issue is...

clarification example

1

I think it would be helpful to explain a top level example that immediately references the binding like: ```mjs import a from 'a' with {lazyInit: true}; a; ```

Cross Realm Interfaces

8

As long as interfaces do not inherit from Object, is it possible to have them be cross realm?

Useful to Node.js Core

23

Node contains a lot of methods that are uncurry the value of `this` in order to safely obtain functionality like `[0, 1].slice()` that is not subject to prototype pollution. This...

node: warn for Object.prototype.__* accessors common in security warnings

11

These accessors cause too much noise in npm security audits for the ecosystem, we should start a path to removal. Figuring out/warning on usage seems a good first step prior...

module: add --package flag for implicit config testing

14

refs: https://github.com/nodejs/node/discussions/37857