Use self-export over ./ export

[guybedford]

This updates the self-import to use the direct self-export form over using ./ as a placeholder for a self-import.

That require('./') inside of CJS packages with exports still works is a legacy path that we should try and deprecate I think, especially since these specifiers cannot be mapped with import maps.

[ljharb]

Not only is this a breaking change, since it won't work in older nodes, but I'm not sure why a relative path wouldn't work with import maps?

Relative paths wil exist forever and can never be deprecated - the solution for forward progress can only ever involve supporting everything that's previously worked.

[guybedford]

Agreed, although it unfortunately means import maps don't work for CommonJS in Node.js.

[ljharb]

I'm confused; why wouldn't import maps in node work with any node-resolvable path? (just like how in browsers, they can work with any browser-resolvable URL)

[guybedford]

Exact trailing slash mappings like "./" are not mappable in import maps, so it implies handling elsewhere in the toolchain.