Guy Bedford

Personally though I see this as something that userland can provide - as mentioned previously using a project like @jdalton's esm to offer this support sounds ideal to me.

> If we remove the directory "default" lookup, does it then (in the interest of simplicity) make sense to remove the package root "default" lookup and only use the package.json...

I don't think it makes it that much more complex: * "module" is the new main, "default.js" is the new "index.js" * automatic extension adding and directory index lookups are...

Some common examples: * `import 'react-dom/server'` * `import '@angular/common/http'`

> Maybe we can use this as an opportunity to better support deep-package paths? In principle I like that deep paths could be disabled in the ESM loader for a...

Really glad to hear there might be interest. Yeah James seems to have dropped quite the bomb with this and it seems really impressive work that will take some time...

> For this reason, while Node.js' HTTP/1.1 client has global agents, a similar concept for HTTP/2 would be difficult to reason about, either node-fetch-global or Node.js-global. Aren't the settings limited...

I wasn't aware it was possible to negotiate an opt-out of push through settings. That sounds like a sensible default then.

@grantila great work, I haven't had a chance to play around with it yet but reading through the readme it looks very promising! And really appreciated for joining the discussion...

I just noticed this project - https://github.com/hisco/http2-client. Since it mimics the http / https APIs that might provide a drop-in path to supporting transparent HTTP/2 in this project? I'm sure...