Guy Bedford
Guy Bedford
@patdx to add some context, Webpack I believe was the source of this behaviour, where RollupJS followed Webpack in discussions with @sokra who had good reasons for it. We can...
It doesn't make a huge difference to users since loads are parallel, but at least from a host consistency perspective, iterating the operations on the imports in pre-order continues to...
@zenparsing what other ways would you see to make explicit deep linking work with this proposal? I'd be very interested to hear what you'd propose here.
Yes it wouldn't apply for that case, this is a new distinction, unlike the main. Allowing arbitrary folders to have a main when importing as absolute or relative could be...
This also supersedes #10.
I've updated this to retain the directory lookups for now, while also ensuring the proper separation between package loading and directory loading that has been historically confused.
If I publish a package as just ESM, transpiler users can use it with the "module" field as they already do through build tools like Parcel, Rollup and Webpack which...
Also tools like `esm` can support the "module" field loading in legacy non-module NodeJS.
Yes, top-level await is a language feature that can't be transpiled (kinda like proxies really).
@zenparsing as far as I'm aware there aren't any implementation hurdles against synchronous ES module instantiation in the v8 API, but for Node: 1. The entire module pipeline is built...