I also don't think you have the correct responsibility analysis here. Are you aware that require-yield is recommended by ESLint core, or that require-await is also a core rule, or that, in general, linters aren't just to "catch bugs"?

That's a very skewed depiction of the rule. It requires async to be licensed by an await, the same way require-yield (which is a core rule) requires generators to be licensed by a yield, or no-extraneous-calss requires classes to be licensed by an instance property.

Bon courage !! Ton français rattrapera très rapidement celui de tes contemporains dès que tu seras là-bas 😃

It will be in Firefox 135 behind a flag, and other browsers are still working on it. If all things go well it should be GA late this year.

Isn't that what Yarn PnP does?

You want 4. Those who can't but know how to tickle ChatGPT the right way to get a solution. They actually deliver anything you ask for.

Out of curiosity is stage 3 a sufficient condition for implementation issues? I imagine the "research phase" should start before stage 3 and stage 3 should be for "experiment phase" and "shipping phase" already?

Would be useful to have links to implementation issues too, so we know how close we are to stage 4 (and to documentation inclusion)

I just think there should be a way to customize module resolution in any env—Node or HTML or workers. What about the Worker() constructor since the type is also specified there?

Sorry too busy to write docs outside of JS lang :( Typically Web API docs are written by people tasked by either FF or Chrome, so if Google cares enough you would see it when Chrome ships it, otherwise you would definitely see it when FF ships it!

Welp, time to make another pedantic MDN PR I guess

TIL that webpack is not capitalized! But their blog uses "Webpack" at start of sentence though: webpack.js.org/blog/2020-10...

Casing police list:
{Type,Java}Script
ESLint
typescript-eslint (even at start of sentence)
npm (even at start of sentence)
Wasm
Git
GitHub
VS Code