strict-ts-lib-v5.0

strict-typescript-lib

Usage

This project ships a strict rewrite of TypeScript's built-in library declarations (lib.es5.d.ts, lib.dom.d.ts, …), one set per TypeScript minor version. Every built-in library lives inside one package, so one dependency and one paths entry is the whole setup, on any package manager.

Each TypeScript minor has its own package — strict-ts-lib-v7.0 for TypeScript 7.0, strict-ts-lib-v5.9 for 5.9, and so on. All minors share one version number, so strict-ts-lib-v7.1@0.5.0 and strict-ts-lib-v7.0@0.5.0 are the same generation of the library.

1. Install the package

npm install -D strict-ts-lib-v7.0     # pnpm add -D / yarn add -D work the same

npm is the only channel. It is a single direct dependency, which every package manager accepts without configuration. (pnpm rejects URL dependencies only when a dependency of a dependency uses one — which is what an earlier layout, one package per lib behind an umbrella, ran into.)

2. Point TypeScript at the libs

The package carries both flavors, named the way TypeScript asks for them, so one wildcard covers all of them — and choosing a flavor is choosing which directory that wildcard points at:

Directory	Numbers
libs/	plain number
libs-branded/	branded (Uint8, SafeUint, …), from ts-type-forge

// tsconfig.json
{
    "compilerOptions": {
        "libReplacement": true, // TypeScript 6.0 and later; see below
        "paths": {
            "@typescript/lib-*": ["./node_modules/strict-ts-lib-v7.0/libs/*"],
            // …or "libs-branded/*" for the branded flavor
        },
    },
}

Two things to watch, because both fail silently — the replacement simply does not happen, with no error and no warning:

• paths is replaced, not merged, by a config that extends another. A package whose own tsconfig.json sets paths for anything else needs this entry repeated there; putting it only in the shared base config is not enough.
• The path is relative to the config that contains it. From a package in a monorepo that is usually ../../node_modules/strict-ts-lib-v7.0/libs/*.

To confirm it took effect, compile something that only the strict library rejects:

echo "export const n = parseInt('10', 1);" > probe.ts
npx tsc --noEmit probe.ts   # strict lib: radix 1 is an error; stock lib: no error

tsc --traceResolution is the fuller check — every @typescript/lib-* lookup it prints should end in was successfully resolved.

TypeScript version support

• >=5.0 <=7.0 — Supported (v5.0–v7.0 published, on npm and as GitHub Release assets). Use the strict-ts-lib-vX.Y matching your minor; the package's peerDependencies pins the range it was generated for. On TypeScript 6.0 and later, set "libReplacement": true in your tsconfig.json compilerOptions — it no longer defaults to on, and the paths entry above does nothing without it.
• <5.0 — Not supported.
• >7.0 — No matching version yet; use the closest published minor.

License

This project is licensed under the Apache License 2.0.