Guy Bedford

Note it would still be an option for us to allow files without an extension for the Node.js CLI entry point only, as we had previously, which was specially implemented...

~~Great point, agreed this should be `MODULE_NOT_FOUND` for both.~~ Update - see below.

`ERR_MODULE_NOT_FOUND` was actually an intentional upgrade path in the ESM resolver since all Node.js error codes start with `ERR_` these days. If we want to change it to `MODULE_NOT_FOUND` though...

The status is still: - CJS resolver throws MODULE_NOT_FOUND - ESM resolver throws ERR_MODULE_NOT_FOUND - configuration errors throw ERR_INVALID_PACKAGE_CONFIG for both As a user, you will either be calling the...

@jkrems we were discussing a multi-major deprecation of path exports. At the current rate of progress on anyone having a clue how to build a standard around `import.meta.resolve` this is...

Ah that's an interesting case. Does that work currently with exports resolution to resolve eg index? If so, I'm not sure the group as a whole made a decision to...

@ljharb I wrote the PR and I didn't know about this case! I disagree in thinking the answer to the fact that `require('pkg/')` with an `"exports": { "./": "./" }`...

@ljharb what is exposed and what is actually used are two different things though. We still have an opportunity to fix minor issues like this that may have slipped through.

Agreed there is inconsistency here between the docs and implementation, so we should change one or the other.

Furthermore, if `--loader` is the primary mechanism if we have a good example loader. The one mentioned is no longer supported since the deprecation of `dynamicInstantiate`.