Node.js Compatibility (@tsonic/nodejs)

Tsonic targets the .NET BCL by default. If you want Node-style APIs (like fs, path, crypto, net, process, etc.), use @tsonic/nodejs.

This is not Node.js itself, and it is not a byte-for-byte clone of the Node standard library. It is a curated, Node-inspired API surface implemented on .NET for Tsonic projects.

Table of Contents

Getting Started

1. Getting Started - enable @tsonic/nodejs in a Tsonic project
2. Importing Modules - what to import from @tsonic/nodejs/index.js vs submodules

Modules

3. console
4. path
5. fs
6. Buffer
7. events
8. timers
9. process
10. os
11. util
12. assert
13. performance
14. stream
15. readline
16. querystring
17. zlib
18. crypto
19. tls
20. X509 / Certificate
21. dns
22. net
23. dgram
24. child_process
25. http (separate submodule)

Overview

In Tsonic projects you import Node-style APIs from @tsonic/nodejs/index.js:

import { console, fs, path } from "@tsonic/nodejs/index.js";

export function main(): void {
  console.log(path.join("a", "b", "c"));
  const text = fs.readFileSync("./README.md", "utf-8");
  console.log(text);
}

Some namespaces are emitted as separate ESM entry points (for example nodejs.Http), and you import those via a subpath:

import { http } from "@tsonic/nodejs/nodejs.Http.js";

Relationship to @tsonic/js

• @tsonic/js provides JavaScript runtime APIs (e.g. JSON, JS-style console, timers).
• @tsonic/nodejs provides Node-style APIs (e.g. fs, path, crypto, http).

You can enable either or both in a project.