compat: tracking issue for Vite

[kt3k]

This issue tracks the issues for executing basic example of vite in compat mode

A typical workflow we try to support is:

yarn create vite
cd vite-project
yarn
yarn dev

With deno compat mode warpper script (the script should be named node and in your $PATH):

#!/bin/sh
DENO_NODE_COMPAT_URL=file:///path/to/your/deno_std/ deno run --no-check --unstable --compat -A $@

(DENO_NODE_COMPAT_URL=... part is optional)

• Not implemented: ChildProcess.unref() used in esbuild
• Not implemented: ChildProcess.ref() used in esbuild
• Internal server error: require$$0$5.URLSearchParams is not a constructor thrown in dev server runtime feat(node): export URLSearchParams via url module #2056
• Internal server error: fs__namespace.createReadStream is not a function thrown in dev server runtime node: add ReadStream and createReadStream #1435
• 'upgrade' event is not implemented on http.Server
  • used here https://github.com/vitejs/vite/blob/c7fc7c34029f109bb716c6a2888022b2f4c40e3d/packages/vite/src/node/server/ws.ts#L39
  • node: implement 'upgrade' event in http.Server #2061
• process.stdout.clearLine is not a function
• node: fs.existsSync throws when returning false in Node #2494

[bartlomieju]

Tentative implementation of ReadStream: #1435

[lino-levan]

Is this issue still relevant since the --compat flag has been removed? Vite support is more or less here (minus the need for the node_modules folder, rollup seems blocked on that) from what I've seen from community projects

[kt3k]

Let's close this as the basic features of vite work now via npm: specifier.

ref: https://www.youtube.com/watch?v=Zjojo9wdvmY

Is this issue still relevant since the --compat flag has been removed?

npm module compatibility issues are still relevant. Please replace --compat part with npm: specifier when reading them. --compat and npm: uses the same underlying API shims (which is std/node). So many issues should apply for both.