Import Patterns

ESM rule first

Tsonic follows ESM-style import specifiers. Use explicit .js subpaths where appropriate.

Local relative import

import { add } from "./math.js";

CLR import

import { Console } from "@tsonic/dotnet/System.js";

Node module import

import * as fs from "node:fs";
import * as path from "node:path";

Requires:

• workspace surface @tsonic/js
• installed package @tsonic/nodejs

Source package import

import { clamp } from "@acme/math";

Works when @acme/math is a Tsonic source package with a compatible tsonic.package.json manifest.

Package-root import

You can still import a source package explicitly by subpath:

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

Dynamic import

Dynamic import() is not part of emitted Tsonic code.

Use static ESM imports instead:

import * as mod from "./module.js";
import "./side-effect.js";

Rejected:

await import(specifier);
await import("some-package");
await import("./module.js");

The import graph must be closed-world and resolvable before IR lowering.