tslib
The runtime library that houses TypeScript's compiler helper functions so your emitted code stays small.
Repository Health
Technical Analysis
tslib is Microsoft’s runtime library containing every helper function the TypeScript compiler would otherwise inline into each emitted file - things like __extends, __assign, __awaiter, __decorate, and __spreadArray. When you enable the importHelpers compiler flag, TypeScript emits a single require(“tslib”) reference instead of redeclaring these helpers in every module.
The result is smaller output on average and less duplicated runtime code across a project or bundle. tslib ships in UMD, ES module, and native .mjs formats with full type declarations, has zero runtime dependencies, and is one of the most widely depended-upon packages in the JavaScript ecosystem.
What You Get
- A single shared copy of all TypeScript helper functions (__extends, __assign, __awaiter, __decorate, __spreadArray, and more) instead of duplicated inline declarations in every emitted module.
- Multiple distribution formats - UMD (tslib.js), ES modules (tslib.es6.js), and native ESM (tslib.es6.mjs) with a modules/ named-export layer - resolved automatically via the package.json exports map.
- Complete TypeScript type declarations (tslib.d.ts) with JSDoc on every helper, so tooling and editors understand the runtime.
- Zero runtime dependencies and a tree-shakeable, side-effect-free package that bundlers can prune down to only the helpers you actually use.
Common Use Cases
- Reducing bundle size in libraries and applications by enabling importHelpers so helper code is shared rather than inlined per file.
- Shipping npm libraries that downlevel modern syntax without bloating consumers with repeated helper boilerplate.
- Providing the runtime helpers required by frameworks like Angular, which depend on tslib for their compiled output.
- Standardizing helper emission across a large TypeScript monorepo so every package references one shared implementation.
Under The Hood
Architecture
tslib is organized around a single hand-authored source of truth: tslib.js defines every helper (__extends, __assign, __awaiter, __generator, __spreadArray, __decorate, __classPrivateFieldGet, __addDisposableResource, and the rest) inside a UMD wrapper that works under CommonJS, AMD, and global script loading. Parallel builds - tslib.es6.js and tslib.es6.mjs - expose the same helpers as ES modules, and a thin modules/index.js layer destructures the default export into individually named ESM exports so bundlers can tree-shake. The package.json exports map routes Node ESM, bundler module resolution, and legacy require() consumers to the correct artifact, while tslib.d.ts supplies types for all formats.
Tech Stack
The library is written in plain JavaScript and TypeScript declarations with zero runtime dependencies. It ships UMD, ESM, and native .mjs formats plus a complete .d.ts, coordinated through the package.json exports field and the sideEffects:false flag that marks it safe to prune. There is no heavy build toolchain - the distributed files are the source - and the code deliberately mirrors the helpers the TypeScript compiler emits so the two stay in lockstep.
Code Quality
Correctness is validated through integration tests rather than unit tests: the test/ directory runs the package through real consumers - Node ESM (exportStructure.test.js, rewriteRelativeImportExtension.test.js), plus webpack, rollup, and vite fixtures orchestrated by runTests.js - to confirm every module format resolves and every export is reachable across bundlers. Helper names follow TypeScript’s own emit conventions exactly, and each is documented with JSDoc in tslib.d.ts, keeping the public surface predictable.
API Design
The developer experience is intentionally invisible: users never call tslib helpers directly. Enabling the importHelpers compiler flag is the entire integration, after which TypeScript rewrites its emitted helper references to pull from tslib automatically. This zero-boilerplate design means the ergonomic surface is a single tsconfig option, while the fully typed, JSDoc-annotated declarations keep editors and type-checkers accurate for the rare cases where the helpers are referenced explicitly.
Used by 81 apps in this directory
highlight.io
Analytics · Developer Tools · Monitoring
Open-source full-stack monitoring that unifies session replay, error tracking, logging, and distributed tracing so you can stop context-switching between tools.
GraphQL Hive
Developer Tools · Devops · Monitoring
Open-source GraphQL schema registry and observability platform with breaking change detection, federation support, and CI/CD integration for teams of any size.
Hoppscotch
Developer Tools
A lightweight, offline-capable API development ecosystem for testing HTTP, GraphQL, WebSocket, MQTT, and SSE endpoints across web, desktop, and CLI.
HyperDX
Analytics · Developer Tools · Monitoring
Open source observability platform that unifies logs, traces, metrics, and session replays on ClickHouse — now the core of ClickStack.
Jan
AI Assistants
Run LLMs 100% locally with full privacy, or connect to cloud AI — your machine, your data, your control.
Jitsu
Data Engineering
Open-source, fully-scriptable data ingestion engine that streams events from web, apps, and APIs to any data warehouse in real time.
Joplin
Note Taking
The privacy-first, open-source note-taking app with end-to-end encrypted sync, AI assistance, and a powerful plugin ecosystem across every platform.
Khoj
AI Assistants · Knowledge Management · Productivity
A self-hostable AI second brain that chats with your documents, searches the web, builds custom agents, and runs entirely on your own LLM.
Kibana
Analytics · Monitoring
Your open source window into the Elastic Stack — query, visualize, and act on data stored in Elasticsearch with real-time dashboards, AI-assisted search, and automated alerting.