Tierney Cyren

I can work on this - I'll send a PR in the next few days.

Yes, that would work.

+1. I also don't get messages saying that someone has been promoted.

+1 to the idea

> We would like to see use cases around sharing these configs, with a plan to pave those paths as they come up. I have hundreds of internal JavaScript repos....

-1 on having npm check this. This should be tooling built by the ecosystem, not something Node.js nor npm maintain. Also, having npm do this would not actually solve the...

> The way I see it is this: it's either pain for (Vite / Node.js server) users, or npm validates ESM. @brillout npm validating ESM will not solve the problem...

>We file bugs against them that their validations are not following the Node.js spec, which is pretty well defined. This would duplicate the work across the three existing package managers,...

More specifically, the exact lines with issues in that JSON: 1⃣https://gist.github.com/bnb/bcc9394cfd81bd61ffdb9b3d303b799b#file-electron-api-json-L470 2⃣https://gist.github.com/bnb/bcc9394cfd81bd61ffdb9b3d303b799b#file-electron-api-json-L701 3⃣https://gist.github.com/bnb/bcc9394cfd81bd61ffdb9b3d303b799b#file-electron-api-json-L862 4⃣https://gist.github.com/bnb/bcc9394cfd81bd61ffdb9b3d303b799b#file-electron-api-json-L882

Added the docs + updated the EoL message to be a bit more correct in this situation.