-
Notifications
You must be signed in to change notification settings - Fork 12.5k
Nightly drops
A nightly build from the main branch is published nightly to NPM and NuGet. Here is how you can get it and use it with your tools.
npm install -g typescript@next
Note: You'll need to configure your project to use the NuGet packages. Please see Configuring MSBuild projects to use NuGet for more information.
The nightlies are available on https://www.myget.org/gallery/typescript-preview
There are two packages:
-
Microsoft.TypeScript.Compiler
: Tools only (tsc.exe
,lib.d.ts
, etc.) . -
Microsoft.TypeScript.MSBuild
: Tools as above, as well as MSBuild tasks and targets (Microsoft.TypeScript.targets
,Microsoft.TypeScript.Default.props
, etc.)
-
Install the npm package
npm install typescript@next
, to your localnode_modules
folder. -
Update,
.vscode/settings.json
with the following:"typescript.tsdk": "<path to your folder>/node_modules/typescript/lib"
-
Install the npm package
npm install typescript@next
, to a localnode_modules
folder, then -
Update the
Settings - User
file with the following:"typescript_tsdk": "<path to your folder>/node_modules/typescript/lib"
More information is available at: https://github.com/Microsoft/TypeScript-Sublime-Plugin#installation
News
Debugging TypeScript
- Performance
- Performance-Tracing
- Debugging-Language-Service-in-VS-Code
- Getting-logs-from-TS-Server-in-VS-Code
- JavaScript-Language-Service-in-Visual-Studio
- Providing-Visual-Studio-Repro-Steps
Contributing to TypeScript
- Contributing to TypeScript
- TypeScript Design Goals
- Coding Guidelines
- Useful Links for TypeScript Issue Management
- Writing Good Design Proposals
- Compiler Repo Notes
- Deployment
Building Tools for TypeScript
- Architectural Overview
- Using the Compiler API
- Using the Language Service API
- Standalone Server (tsserver)
- TypeScript MSBuild In Depth
- Debugging Language Service in VS Code
- Writing a Language Service Plugin
- Docker Quickstart
FAQs
The Main Repo