TypeScript with Node.js

Node.js executes JavaScript outside the browser and provides server-side APIs, such as process information and filesystem access. TypeScript adds static checks during development, while Node executes JavaScript after compilation or uses a supported type-stripping workflow. Node does not provide a browser DOM by default.

The node:process module exposes genuine Node runtime values. The version string supplies its major component; the platform is a non-empty identifier. This does not depend on browser globals.

Node does not supply document, localStorage, or browser-specific constructors in ordinary server scripts.

Save as node-js.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

import { version, platform } from "node:process";
console.log(`Node major: ${version.split(".")[0].replace("v", "")}`);
console.log(`Platform known: ${platform.length > 0}`);

Verified output

Node major: 22
Platform known: true

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

The example runs in Node.js 22.16.0; if it reads runtime environment details, your displayed values may differ.

The node:process module exposes genuine Node runtime values. The version string supplies its major component; the platform is a non-empty identifier. This does not depend on browser globals.

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

Node does not supply document, localStorage, or browser-specific constructors in ordinary server scripts.

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

Use process.argv to read an optional name and print a greeting with a reasonable default.

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.

Node.

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