Guy Bedford

Interaction with import assertions

1

This interaction needs to be clearly defined and documented in a way that does not conflict with that specification.

Consider wider evaluator attribute possibilities

5

Currently the proposal is entirely justified around the Web Assembly use case. Typically the MIME type for fetch schemes, or the file extension for file schemes is considered the authoritative...

import.meta.resolve second argument

1

Chrome is now moving towards shipping `import.meta.resolve` as discussed in https://github.com/denoland/deno/issues/7296. The current form takes a single argument to resolve. Node.js implements the ability to pass an optional second argument...

path.scope.hasBinding doesn't seem to reflect new top-level declarations

7

I just noticed this edge case of the System module format output. If I apply a transform that adds a new top-level binding, then the `path.scope.hasBinding` in the system module...

Update chalk dependency

3

### 💻 - [ ] Would you like to work on this feature? ### What problem are you trying to solve? I've just been running Babel core in Deno using...

Explicit deep linking

3

If we make package deep linking explicit for ES packages, we could treat all other deep links as CommonJS resolutions by default. That is, users would need to opt-in to...

Implement resolver feature separations

2

As described in #16, this separates the features of the resolver to make this specification as minimal as possible in the decisions it imposes. The hope here is that by...

Supporting CommonJS subpaths

3

This is kind of the main drawback of this proposal, and I'm just wondering if there might not be a way to handle it. Currently the switch is treated as...

Separating this spec from extension handling and directory lookups

1

The discussion in https://github.com/zenparsing/node-default-module-proposal/issues/15 is actually a general discussion that applies to the ES resolver regardless of this spec. I'm wondering if perhaps we shouldn't separate this specification from such...

Consider removing support for "default.js" directory lookups

4

I really like that this proposal includes removing the file extension checks, as this will help get closer to code that works in browsers as well. In line with this,...