Open noelforte opened 1 month ago
Those docs (https://docs.deno.com/api/node/) are automatically generated based on type definition files from @types/node. Perhaps it's only intended to be a reference for what Node supports in order for Deno developers to not be dependent on Node's docs.
The actual Node compatibility documentation is at https://docs.deno.com/runtime/reference/node_apis/.
Ideally what should have happened is we start with a particular @types/node version and document Deno's compatibility at that point. Then every time @types/node is bumped, review the changes and update the compatibility list. That's certainly quite a lot of work!
That's certainly quite a lot of work!
I don't doubt it! Thanks for clearing it up. Feel free to close as a duplicate of https://github.com/denoland/deno/issues/24945.
Just came across this aswell, work around using https://jsr.io/@libs/crypto
import { hash } from "@libs/crypto";
Possibly related: https://github.com/denoland/deno/issues/24945
Implementation and example usage of the
.hash()
method fromnode:crypto
is a documented part of Deno's Node-compatible API.However, attempting to run the following example throws an error:
Documented features should be supported or removed from the documentation until actually implemented.