Install typescript with Homebrew, apk, chocolatey, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• tsc
• tsserver

Project history

Microsoft introduced TypeScript publicly with TypeScript 0.8 in October 2012 and released TypeScript 1.0 on April 2, 2014. The 1.0 announcement described a year and a half of community growth around large-scale JavaScript applications, declaration files, Visual Studio tooling, npm distribution, and source availability.

The 1.0 release also marked an opening toward external contributions: Microsoft announced that the compiler and language service would begin accepting pull requests. Later official release writing noted that the repository moved to GitHub around the 1.1 era to encourage community engagement and collaboration.

By TypeScript 2.0 in September 2016, Microsoft described the project as a broader language, tooling, and community ecosystem. The 2.0 announcement highlighted ECMAScript alignment, JavaScript library support, the language service, Angular 2 adoption, strict null checking, and the move from separate declaration-file package managers toward the scoped `@types` npm workflow.

In the 5.x and 6.x era, TypeScript remained both a compiler package and the core of editor tooling. Microsoft release posts continue to emphasize type-checking, editor services such as completion, navigation, and refactors, and npm as the standard distribution path. The 2025 native TypeScript announcement opened a new performance-focused chapter by previewing a native-code port of the compiler and toolset.

Adoption history

TypeScript adoption grew through the combination of npm packaging, Visual Studio and VS Code integration, declaration files for JavaScript libraries, and framework adoption. The TypeScript 2.0 announcement said npm downloads had grown from 275,000 in one month to more than 2 million in the comparable month the following year, and described DefinitelyTyped as a central community asset with thousands of libraries and contributors.

Angular 2 adoption was an important early framework milestone because it validated TypeScript for a major JavaScript application framework. Over time, TypeScript became a default choice for application-scale JavaScript, library authoring, frontend frameworks, backend Node.js services, and editor-powered JavaScript development.

How it is used

Package users install TypeScript primarily for the `tsc` compiler and `tsserver` language service. `tsc` type-checks projects and emits JavaScript, while `tsserver` powers editor intelligence such as completions, navigation, quick fixes, rename, refactors, and inlay information.

In package-manager culture, TypeScript is almost always paired with `tsconfig.json`, npm scripts, editor plugins, declaration packages under `@types/*`, and build tools that either call `tsc` directly or use TypeScript syntax through bundlers and transpilers.

Why package nerds care

TypeScript is one of the defining package-manager-era developer tools. It made a compiler and language service a normal dev dependency, pushed type declarations into the npm package graph, and helped make editor feedback, CI type checks, and generated JavaScript build artifacts routine parts of JavaScript packages.

For Homebrew and distro users, the formula is also a convenient way to install the global `tsc` and `tsserver` binaries outside a single npm project, useful for editors, scripts, and system-level developer environments.

Timeline

• 2012: TypeScript 0.8 introduced the language publicly.
• 2014: TypeScript 1.0 shipped with Visual Studio, npm, and source distribution.
• 2014: The compiler and language service began opening to pull requests, and the project moved toward GitHub collaboration.
• 2016: TypeScript 2.0 shipped with strict null checking, ECMAScript alignment, language-service improvements, and the `@types` npm workflow.
• 2025: Microsoft announced native TypeScript work aimed at large performance gains for the compiler and toolset.
• 2026: TypeScript 6.0 release artifacts continued the npm-centered release model.

Related projects

• Related projects include JavaScript, ECMAScript, Node.js, npm, DefinitelyTyped, VS Code, Visual Studio, `tsserver`, TypeScript Language Server, Angular, Babel, esbuild, swc, and the native TypeScript Go implementation.

Sources

• https://devblogs.microsoft.com/typescript/a-10x-faster-typescript/
• https://devblogs.microsoft.com/typescript/announcing-typescript-1-0/
• https://devblogs.microsoft.com/typescript/announcing-typescript-2-0/
• https://github.com/microsoft/TypeScript#readme
• https://github.com/microsoft/TypeScript/releases
• https://www.typescriptlang.org/docs
• source_facts.package-manager