Running TypeScript with Native Runtime Support

Some modern runtimes run TypeScript by stripping erasable type syntax directly. In Node.js, this is limited support: the built-in loader does not honor tsconfig.json, type-check code, or transform all TypeScript constructs. For predictable builds and older runtimes, keep a tsc + node or suitable toolchain workflow.

The Profile annotation can be erased without changing the JavaScript logic. In Node versions with built-in type stripping enabled, such erasable syntax can execute directly, but compatibility depends on the installed Node release.

Native TypeScript execution is not the same as TypeScript type checking; run tsc --noEmit separately.

Save as running-native-runtime-support.ts. The following program passed strict TypeScript compilation, and the displayed output was captured by executing its emitted JavaScript with Node.js 22.16.0.

TypeScript source

type Profile = { name: string };
const profile: Profile = { name: "Maya" };
console.log(`Hello, ${profile.name}`);

Verified output

Hello, Maya

Compile: npx tsc --strict --target es2022 --module commonjs running-native-runtime-support.ts; run: node running-native-runtime-support.js. For Node.js API examples, install @types/node first. For browser projects, use the browser-specific instructions below.

The example demonstrates the code-level behavior; the related configuration or test commands are shown separately when needed.

The Profile annotation can be erased without changing the JavaScript logic. In Node versions with built-in type stripping enabled, such erasable syntax can execute directly, but compatibility depends on the installed Node release.

Predict what changes if you alter one input. Then run the code to compare your reasoning with the real output.

Practical project lab: These are real configuration and source-file examples, not a TypeScript object that merely describes settings. Place the files at the named paths relative to one project directory.

hello.ts

type Name = { first: string };
const user: Name = { first: "Maya" };
console.log(user.first);

Commands

node --version
node hello.ts
npx tsc --noEmit hello.ts

Node must be a version with default type stripping; earlier Node 22 versions require an explicit experimental flag.

This project requires its named external tool or dependency and was supplied as setup guidance; it was not claimed as an executed test here.

Native TypeScript execution is not the same as TypeScript type checking; run tsc --noEmit separately.

Identify whether the failure is a type-checking issue, a configuration issue, or a runtime behavior issue before choosing a fix.

Inspect node --version. Test node example.ts only on a compatible Node release, then run tsc --noEmit independently.

Write down your expected result first. For configuration examples, compare compiler output and diagnostics; for test examples, make the assertion fail deliberately to verify that the tool reports it.

For the exact current options and platform behavior, consult the official documentation. These examples were verified using the tool versions described above.

Some modern runtimes run TypeScript by stripping erasable type syntax directly.

Run the primary example, then complete the practice task or environment-specific lab.