You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deno has a Node compatibility layer. I'm currently using it for a few operations in @lishaduck/effect-platform-deno that rely on fids. However, the node:* modules don't come with types. The docs recommend installing @types/node, but this both augments the globals (e.g., it shows Buffer as available) and isn't kept in sync with Deno's TS and Node support. For example, until #26950 is completed, the latest @types/node doesn't work with Deno, and it'd also be nice to get deprecation warnings on things that the Node-compat layer doesn't support.
The text was updated successfully, but these errors were encountered:
Maybe we should wait for Node to support TypeScript, so we can have more stable typing.
I haven't seen anything about Node taking over maintenance of @types/node as part of the ts work.
That'd be great, but I don't foresee it happening anytime soon—I believe Node uses a custom JSDoc-like comment-based dsl for documenting types.
Deno has a Node compatibility layer. I'm currently using it for a few operations in
@lishaduck/effect-platform-deno
that rely on fids. However, thenode:*
modules don't come with types. The docs recommend installing@types/node
, but this both augments the globals (e.g., it showsBuffer
as available) and isn't kept in sync with Deno's TS and Node support. For example, until #26950 is completed, the latest@types/node
doesn't work with Deno, and it'd also be nice to get deprecation warnings on things that the Node-compat layer doesn't support.The text was updated successfully, but these errors were encountered: