- Compatible with all JavaScript syntax, and extend the syntax based on JS;
- Statically analyze the code to find the code that is likely to have BUG;
- Generate pure JavaScript code without any optimization or processing of the code, even errors in the source code are retained in the generated code;
- Does not affect the runtime environment of the generated code.
├── bin # the final tsc and tsserver commands for users
├── doc # language specification document
├── lib # system standard library and localization of prompt information, LKG
├── loc
│ └── lcl # error message localization
├── scripts # tool scripts when developing projects
├── src # source code
│ ├── compiler # compiler source code
│ │ ├── transformers # transformers with different target syntax
│ │ ├── scanner.ts # grammar analysis: scan a single file, lexical analysis
│ │ ├── parser.ts # grammar analysis: get tokens to generate AST tree, syntax analysis
│ │ ├── binder.ts # semantic analysis: analysis scope, create symbol table; analysis process, create flow diagram
│ │ ├── checker.ts # semantic analysis: type checking, do semantic analysis
│ │ ├── transformer.ts # optimization generation: syntax conversion and polyfill
│ │ ├── emitter.ts # optimization generation: JS code generation
│ │ ├── system.ts # tools: OE
│ │ └── types.ts # tools: key data structures and interfaces
│ └── services # language service, mainly used by VSCode. Searching for definitions and other functions
└── tests # test
See: More Details
There are many ways to contribute to TypeScript.
- Submit bugs and help us verify fixes as they are checked in.
- Review the source code changes.
- Engage with other TypeScript users and developers on StackOverflow.
- Help each other in the TypeScript Community Discord.
- Join the #typescript discussion on Twitter.
- Contribute bug fixes.
- Read the language specification (docx, pdf, md).
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
In order to build the TypeScript compiler, ensure that you have Git and Node.js installed.
Clone a copy of the repo:
git clone https://github.com/microsoft/TypeScript.gitChange to the TypeScript directory:
cd TypeScriptInstall Gulp tools and dev dependencies:
npm install -g gulp
npm installUse one of the following to build and test:
gulp local # Build the compiler into built/local.
gulp clean # Delete the built compiler.
gulp LKG # Replace the last known good with the built one.
# Bootstrapping step to be executed when the built compiler reaches a stable state.
gulp tests # Build the test infrastructure using the built compiler.
gulp runtests # Run tests using the built compiler and test infrastructure.
# Some low-value tests are skipped when not on a CI machine - you can use the
# --skipPercent=0 command to override this behavior and run all tests locally.
# You can override the specific suite runner used or specify a test for this command.
# Use --tests=<testPath> for a specific test and/or --runner=<runnerName> for a specific suite.
# Valid runners include conformance, compiler, fourslash, project, user, and docker
# The user and docker runners are extended test suite runners - the user runner
# works on disk in the tests/cases/user directory, while the docker runner works in containers.
# You'll need to have the docker executable in your system path for the docker runner to work.
gulp runtests-parallel # Like runtests, but split across multiple threads. Uses a number of threads equal to the system
# core count by default. Use --workers=<number> to adjust this.
gulp baseline-accept # This replaces the baseline test results with the results obtained from gulp runtests.
gulp lint # Runs eslint on the TypeScript source.
gulp help # List the above commands.
node built/local/tsc.js hello.ts