packages/browser-node

[lemanschik]

the browser node package

• compile NodeJS to wasm nodejs/help#3774

running nodejs as wasm modules is the right thing to do anyway the most time only fs and net is needed and stdio that are the core interfaces.

• net
• fs
• stdio
• crypto is in all environments already
• net is in all environments but not all protocols we need to port from curl

we in fact demonstrated that via the just-js project where v8 builds v8 with its modules independent maybe that can get turned into a wasm build the most things that they did is the network layer over the serviceWorker thats it.

we do not even need that hackish stuff we have directly file system access api and we have direct sockets api both form the links to fs and net.

while fs on linux for example also already leads alone to full network access as every device is a file you can write directly to sockets and devices.

i can supply the needed browser apis to implement vm and such stuff including atomic workers and that.

• NodeJS API Docs. lemanschik/web-modules#7

we run rollup and adapt the result of that as build cache

node -e 'console.log(process.binding("natives"))'

that are node js internals as js strings already formatted as object no need to use the files .

later iterations will replace wasm with the new mksnapshot module format.