npm compat tracking issue

[kt3k]

Tracking issue for npm/node compat issues in std/node

Note: Currently we are moving Node polyfill implementation from std/node (this repository) to ext/node (Deno main repository). ref. #17724

Please wait for a while to contribute to node compat layer

High priority items

• socket option in tls.connect node: support socket option in tls.connect #17842 (affects npm:mssql)
• http(s) requests can't upgrade to websocket requests
  • "https" and "http" deno compatibility shims do not support WebSocket connections #17846 [Node Compat] http.ClientRequest does not emit upgrade event (or is buggy) #17847 (affects npm:discord.js)
  • Unexpected server response: 101 running puppeteer from npm specifier #17496 (affects npm:puppeteer, npm:ws)
  • NPM: Playwright does not work #16899 (affects npm:playwright)
• http.ClientRequest.setTimeout compat(node/https): ClientRequest.setTimeout is not a function #17852 deno run -A npm:aws-cdk destroy throws process is not defined #18198 (affects npm:aws-cdk-lib)
• crypto.Sign node: add crypto.Sign #17843
• crypto.createSecretKey Node compat crypto.createSecretKey #17844 (affects npm:next-auth, npm:jsonwebtoken)
• npm:aws-cdk init throws TypeError npm:aws-cdk init throws TypeError (windows only) std#2916 (affects npm:aws-cdk (windows)

Medium priority items

• crypto.generateKeyPairSync fix(ext/node): implement asymmetric keygen #18651 (affects npm:mineflayer)
• missing APIs in node:os Support missing node/os functionality #17850
• X509Certificate Tracking issue for remaining node:crypto APIs #18455
• node:vm.runInThisContext() Incorrect behavior of node:vm.runInThisContext() #17853
• TypeError: Cannot read properties of undefined (reading 'remoteAddress') compat: tracking issue for npm:json-server #18325
• Use of global process in _events.mjs ReferenceError: process is not defined #17854 (affects npm:bullmq
• primisify(execFile) Promisified execFile returns undefined in Deno std#3145
• crypto.Cipheriv Node compatibility: "Uncaught Error: Not implemented: crypto.Cipheriv" #17848 (affects tuyapi) @kt3k
• ...

Note about priorities

The priorities are higher when the issue affects popular npm modules (when used via npm: specifier).

---

[iuioiua]

I'll give crypto.createSecretKey() a crack.

[PolarETech]

I would like to take up promisify(execFile). I have already implemented promisify(exec), so I think this one will be ready to go soon.

[PolarETech]

I have started to try npm:aws-cdk init.

Still investigating, but it seems to be an issue with npm:fs-extra.copy().
Because when the function runs fs.lstat(sourcefile) (== Deno.lstat(sourcefile)) to copy the file permissions, the mode value is null on Windows. In Node.js, it is possible to get the mode value.

I will comment in that issue when the information has been compiled.

[iuioiua]

I'll give crypto.createSecretKey() a crack.

I'm attempting crypto.Sign and crypto.Verify first.

[jacobmischka]

Just to tie together a few related other issues, the http task in high priority also affects npm:ws (#17496 (comment)) itself, and also npm:puppeteer (#17496) and npm:playwright (#16899) for some more notable packages.

[misterjoshua]

@kt3k Here's another AWS CDK-related npm compatibility issue affecting Deno 1.31.2: #18198

[barthuijgen]

Another missing feature I do not see mentioned in any of the linked issues:

Uncaught Error: Not implemented: crypto.Decipheriv.prototype.setAutoPadding

Used as

const cipher = createDecipheriv("AES-128-CBC", "key", "iv");
cipher.setAutoPadding(false);

[bartlomieju]

Closing in favor of #18836