New work activity: Common Minimum Node.js Compat API

[jasnell]

All runtimes end up needing to implement some level of Node.js compatibility. They all end up implementing some subset of Node.js APIs. It makes sense for the committee to definea Common Minimum Node.js Compat API in the same spirit as the Common Minimum Web API

[thescientist13]

Thinking about this from the last meeting, would be curious to see what a baseline list would look like here, and if there's anyway to leverage that list and into pushing harder on Web Standard versions of these (or at least assist in their promotion / evangalism).

A couple basic ones that come to my mind:

• path -> new URL
• fs -> fetch + file:// (or a FileSystem API)

I know personally I would take a web standard implementation any day as that would truly be the most interoperate (and we are the Web Interoperable Runtime TC 😅 ), and those two alone probably make a large percentage of Node APIs used. Then we don't have to risk NodeJS becoming its own implicit "standard" which I feel like is a bit of unfair burden to that project and probably much more of a moving target than web standards even are.