base on Staging repo for development of native port of TypeScript # TypeScript 7 [Not sure what this is? Read the announcement post!](https://devblogs.microsoft.com/typescript/typescript-native-port/) ## Preview A preview build is available on npm as `@typescript/native-preview`. ```sh npm install @typescript/native-preview npx tsgo # Use this as you would tsc. ``` A preview VS Code extension is [available on the VS Code marketplace](https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.native-preview). To use this, set this in your VS Code settings: ```json { "typescript.experimental.useTsgo": true } ``` ## How to Build and Run This repo uses [Go 1.24 or higher](https://go.dev/dl/), [Rust 1.85 or higher](https://www.rust-lang.org/tools/install), [Node.js with npm](https://nodejs.org/), and [`hereby`](https://www.npmjs.com/package/hereby). For tests and code generation, this repo contains a git submodule to the main TypeScript repo pointing to the commit being ported. When cloning, you'll want to clone with submodules: ```sh git clone --recurse-submodules https://github.com/microsoft/typescript-go.git ``` If you have already cloned the repo, you can initialize the submodule with: ```sh git submodule update --init --recursive ``` With the submodule in place and `npm ci`, you can run tasks via `hereby`, similar to the TypeScript repo: ```sh hereby build # Verify that the project builds hereby test # Run all tests hereby install-tools # Install additional tools such as linters hereby lint # Run all linters hereby format # Format all code hereby generate # Generate all Go code (e.g. diagnostics, committed to repo) ``` Additional tasks are a work in progress. `hereby` is not required to work on the repo; the regular `go` tooling (e.g., `go build`, `go test ./...`) will work as expected. `hereby` tasks are provided as a convenience for those familiar with the TypeScript repo. ### Running `tsgo` After running `hereby build`, you can run `built/local/tsgo`, which behaves mostly the same as `tsc`. ### Running LSP Prototype To debug and run the VS Code extension without installing it globally: * Run VS Code in the repo workspace (`code .`) * Copy `.vscode/launch.template.json` to `.vscode/launch.json` * <kbd>F5</kbd> (or `Debug: Start Debugging` from the command palette) This will launch a new VS Code instance which uses the Corsa LS as the backend. If correctly set up, you should see "tsgo" in the status bar when a TypeScript or JavaScript file is open:  ## What Works So Far? This is still a work in progress and is not yet at full feature parity with TypeScript. Bugs may exist. Please check this list carefully before logging a new issue or assuming an intentional change. | Feature | Status | Notes | |---------|--------|-------| | Program creation | done | Same files and module resolution as TS5.8. Not all resolution modes supported yet. | | Parsing/scanning | done | Exact same syntax errors as TS5.8 | | Commandline and `tsconfig.json` parsing | mostly done | Entry point slightly different for now | | Type resolution | done | Same types as TS5.8 | | Type checking | done | Same errors, locations, and messages as TS5.8. Types printback in errors may display differently (in progress) | | JavaScript-specific inference and JS Doc | not ready | - | | JSX | done | - | | Declaration emit | in progress | Most common features are in place, but some edge cases and feature flags are still unhandled | | Emit (JS output) | in progress | `target: esnext` well-supported, other targets may have gaps | | Watch mode | prototype | Watches files and rebuilds, but no incremental rechecking | | Build mode / project references | not ready | - | | Incremental build | not ready | - | | Language service (LSP) | prototype | Minimal functionality (errors, hover, go to def). More features coming soon | | API | not ready | - | Definitions: * **done** aka "believed done": We're not currently aware of any deficits or major left work to do. OK to log bugs * **in progress**: currently being worked on; some features may work and some might not. OK to log panics, but nothing else please * **prototype**: proof-of-concept only; do not log bugs * **not ready**: either haven't even started yet, or far enough from ready that you shouldn't bother messing with it yet ## Other Notes Long-term, we expect that this repo and its contents will be merged into `microsoft/TypeScript`. As a result, the repo and issue tracker for typescript-go will eventually be closed, so treat discussions/issues accordingly. For a list of intentional changes with respect to TypeScript 5.7, see CHANGES.md. ## Contributing This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit [Contributor License Agreements](https://cla.opensource.microsoft.com). When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments. ## Trademarks This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow [Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/legal/intellectualproperty/trademarks/usage/general). Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies. ", Assign "at most 3 tags" to the expected json: {"id":"13792","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"