typescript-native-bridge 0.0.0

package/LICENSE

@@ -0,0 +1,55 @@
+Apache License
+
+Version 2.0, January 2004
+
+http://www.apache.org/licenses/ 
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+You must give any other recipients of the Work or Derivative Works a copy of this License; and
+
+You must cause any modified files to carry prominent notices stating that You changed the files; and
+
+You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+
+If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

package/NOTICE

@@ -0,0 +1,18 @@
+typescript-native-bridge
+Copyright 2026 typescript-native-bridge contributors
+
+This product includes software developed at:
+
+Microsoft TypeScript
+  https://github.com/microsoft/TypeScript
+  Copyright (c) Microsoft Corporation.
+  Licensed under the Apache License, Version 2.0.
+
+Microsoft typescript-go
+  https://github.com/microsoft/typescript-go
+  Copyright (c) Microsoft Corporation.
+  Licensed under the Apache License, Version 2.0.
+
+Modifications by the typescript-native-bridge project (patches/, overlay/, bridge/)
+are noted in the repository history and distributed under the Apache License,
+Version 2.0.

package/README.md

@@ -0,0 +1,448 @@
+# typescript-native-bridge (TNB)
+
+> **Status:** Experimental. Published on npm as [`typescript-native-bridge`](https://www.npmjs.com/package/typescript-native-bridge).
+
+**A faster `typescript` you can drop into any project** (measure on your repo; no fixed speedup guarantee).
+
+Swap the `typescript` package for this fork and keep using `tsc`, `vue-tsc`, ESLint, and your
+editor as before. Type-checking runs on **tsgo** (Microsoft's Go TypeScript compiler) instead
+of JavaScript. You do **not** need to learn tsgo, change imports, or add per-tool config.
+
+---
+
+## Why TNB exists
+
+TNB is a **drop-in `typescript` replacement** — not a separate `tsgo` CLI, not a new
+LSP. One `typescript` override accelerates every tool that calls `getTypeChecker()` through
+the standard Compiler API.
+
+### Three problems one override fixes
+
+**1. `vue-tsc` cannot use standalone `tsgo`**
+
+`vue-tsc` is built on the `typescript` programmatic API + Volar hooks (`extraFileExtensions`,
+virtual `getSourceFile` for `.vue`, `createProgram` wrapping). Standalone `tsgo` / `tsgo
+LSP` does not speak that protocol — you cannot speed up `vue-tsc` by swapping the CLI to
+`tsgo`. TNB keeps `vue-tsc` unchanged and routes `createProgram` → `createTsgoProgram`,
+feeding Volar virtual content to Go via in-process overlays.
+
+**2. ESLint + typescript-eslint type-aware rules are checker-bound**
+
+`@typescript-eslint/parser` imports `typescript` and calls `createProgram` /
+`getTypeChecker()` for type-aware rules. The bottleneck is the JS checker, not ESLint's
+AST walk. TNB makes the parser pick up the fork automatically — no eslint config changes,
+no separate `tsgo` lint pass.
+
+**3. Editors need `tsserver` + Language Service Plugins (not tsgo LSP)**
+
+Volar (`@vue/typescript-plugin`) runs as a **tsserver LS Plugin**. Microsoft's tsgo LSP
+preview does not support that plugin model — migrating the editor means losing `.vue`
+integration. TNB keeps **stock `tsserver` + plugin host**, swapping only the checker
+backend to Go in-process.
+
+### What this means in practice
+
+| Tool | Still uses | Checker engine |
+|---|---|---|
+| `vue-tsc` / `tsc` | `typescript` API (`_tsc.js`) | tsgo |
+| `tsserver` / VS Code | `typescript` + LS Plugins | tsgo |
+| `@typescript-eslint/parser` | `typescript` API | tsgo |
+
+Compare with `@typescript/native-preview`: separate `tsgo` binary, change scripts, editor
+uses experimental tsgo LSP — **does not** cover the three rows above with one override.
+
+---
+
+## 10-minute checklist
+
+Use this if you just want to try TNB on an existing project:
+
+- [ ] Add a `typescript` override (see below)
+- [ ] Run `pnpm install` / `npm install`
+- [ ] Run your usual typecheck (`vue-tsc`, `tsc`, or `nuxi typecheck`)
+- [ ] Confirm the **TNB ACTIVE** banner appears on stderr (first run per process)
+- [ ] **Editor:** set `typescript.tsdk` and switch to the workspace TypeScript version (see [Editor / tsserver](#editor--tsserver-tsdk))
+- [ ] If no banner → see [Troubleshooting](#troubleshooting)
+
+---
+
+## Quick start
+
+### pnpm (monorepos)
+
+Put the override in **`pnpm-workspace.yaml`** at the repo root:
+
+```yaml
+# pnpm-workspace.yaml
+overrides:
+  typescript: npm:typescript-native-bridge@<version>
+```
+
+```bash
+pnpm install
+pnpm exec vue-tsc -b --noEmit    # or your project's typecheck script
+```
+
+If packages use `catalog:typescript`, update the **catalog entry** as well (see
+[Nuxt / Vue / monorepo notes](#nuxt--vue--monorepo-notes)).
+
+### npm
+
+```jsonc
+// package.json
+{
+  "overrides": {
+    "typescript": "npm:typescript-native-bridge@<version>"
+  }
+}
+```
+
+### yarn
+
+```jsonc
+// package.json
+{
+  "resolutions": {
+    "typescript": "npm:typescript-native-bridge@<version>"
+  }
+}
+```
+
+### Local path (developing TNB or pinning a git checkout)
+
+```yaml
+# pnpm-workspace.yaml
+overrides:
+  typescript: link:../typescript-native-bridge
+```
+
+Build the fork first (`npm run setup` in the TNB repo). See [Developing TNB](#developing-tnb-contributors).
+
+After any override change: **reinstall dependencies**. The override applies repo-wide —
+`vue-tsc`, `@typescript-eslint/parser`, and other transitive `typescript` users all pick
+up the fork.
+
+---
+
+## How to tell it's working
+
+On the **first** type-check in a process, TNB prints this banner to **stderr**:
+
+```
+┌─────────────────────────────────────────────────────────┐
+│  ✅  TNB ACTIVE — `typescript` is the tsgo-backed fork  │
+└─────────────────────────────────────────────────────────┘
+```
+
+**No banner = stock `typescript` is still loaded.** See [Troubleshooting](#troubleshooting).
+
+Quick sanity check:
+
+```bash
+node -e "console.log(require.resolve('typescript'))"
+# should point at typescript-native-bridge, not node_modules/typescript@5.x
+```
+
+---
+
+## What you get
+
+| | Stock `typescript` | TNB |
+|---|---|---|
+| Import | `import * as ts from "typescript"` | Same |
+| CLI | `tsc`, `vue-tsc`, `nuxi typecheck` | Same commands |
+| Per-tool config | — | None |
+| Checker engine | JavaScript | Go (tsgo), in-process |
+
+```
+your tool  →  typescript (fork)  →  tsgo (Go)
+              same public API         type-checking
+                    └── in-process bridge (no child process, no IPC)
+```
+
+**API compatibility:** Existing `tsc` / `vue-tsc` / ESLint workflows work without code
+changes. The checker is implemented by tsgo internally; tools that depend on deep
+TypeScript internals or custom emit paths should be validated separately.
+
+---
+
+## Nuxt / Vue / monorepo notes
+
+### pnpm catalog + overrides
+
+If your monorepo uses a **catalog** and any package depends on `typescript` via
+`catalog:`, update the catalog entry **as well as** `overrides:` — otherwise those
+packages may still resolve stock TypeScript even when root `overrides` is set:
+
+```yaml
+# pnpm-workspace.yaml
+catalog:
+  typescript: link:../typescript-native-bridge
+overrides:
+  typescript: link:../typescript-native-bridge
+```
+
+> **Monorepo tip:** Prefer workspace `overrides` only. A root `pnpm add -D typescript@link:...`
+> alone often does **not** replace `vue-tsc`'s transitive `typescript`.
+
+### Nuxt projects
+
+Typical flow:
+
+```bash
+pnpm exec nuxi prepare          # generate .nuxt types first
+pnpm exec nuxi typecheck        # or your package.json "typecheck" script
+```
+
+### Vue / Volar / SFC
+
+**Supported**
+
+- `import App from './App.vue'` resolves to the `.vue` file itself
+- Volar **virtual TypeScript** (content injected via `getSourceFile` when the file
+  isn't on disk) via overlay
+- `.vue`, `.svelte`, `.astro`, `.mdx`, etc. through the standard `extraFileExtensions`
+  contract — no hard-coded `.vue` special case
+- `allowArbitraryExtensions` inferred `true` in tsgo when host extra extensions are
+  present and tsconfig leaves the option unset (explicit `false` opts out)
+
+**Not supported**
+
+- Custom `resolveModuleNames` / `resolveModuleNameLiterals` that remap an import to a
+  **different physical file** (bridge is synchronous JS→Go; tsgo cannot call back into JS
+  resolvers)
+- Explicit `allowArbitraryExtensions: false` in tsconfig → normal `TS6263` (opt-out)
+
+### Editor / tsserver (tsdk)
+
+CLI typecheck (`vue-tsc`, `tsc`) picks up TNB automatically after the override. **The IDE
+does not** — VS Code / Cursor ship their own TypeScript and only use your fork when you
+point **`typescript.tsdk`** at the workspace install and opt in to the workspace version.
+
+After `pnpm install`, `node_modules/typescript` **is** TNB (same layout as stock
+`typescript`: `lib/tsserver.js`, `lib/typescript.js`, …). The editor must load that
+`tsserver`, not the built-in one.
+
+**1. Add workspace settings** (commit `.vscode/settings.json` for the team):
+
+```jsonc
+// .vscode/settings.json — VS Code and Cursor
+{
+  "typescript.tsdk": "node_modules/typescript/lib",
+  "typescript.enablePromptUseWorkspaceTsdk": true
+}
+```
+
+Use a path relative to the **workspace folder** that contains `node_modules` (monorepo:
+usually the repo root). With pnpm overrides this resolves to TNB's `lib/` even when the
+physical path is a symlink.
+
+**2. Switch to the workspace version (required once per machine / workspace)**
+
+Command Palette → **`TypeScript: Select TypeScript Version`** → **Use Workspace Version**.
+
+VS Code deliberately does not run workspace `tsserver` until you confirm (security). The
+prompt appears on first open if `typescript.enablePromptUseWorkspaceTsdk` is set; otherwise
+run the command manually.
+
+**3. Verify**
+
+- Status bar / **TypeScript: Select TypeScript Version** should show a path under
+  `node_modules/typescript/lib`, not "VS Code's Version".
+- Open a `.ts` file and trigger type-checking; **View → Output → TypeScript** may show
+  **TNB ACTIVE** on first project load (same banner as CLI).
+- Vue/Nuxt: keep `@vue/typescript-plugin` in `tsconfig` `compilerOptions.plugins` as today
+  — it runs as a **tsserver LS Plugin** on this fork; no separate tsgo LSP.
+
+| Path | Bundle | Used by |
+|---|---|---|
+| `lib/_tsc.js` | CLI | `tsc`, `vue-tsc -b` |
+| `lib/tsserver.js` → `lib/typescript.js` | Language service | IDE, `tsserver`, LS Plugins |
+
+### CLI vs editor (summary)
+
+| | CLI | IDE |
+|---|---|---|
+| Needs override | Yes | Yes (same `node_modules/typescript`) |
+| Extra config | No | **`typescript.tsdk` + Use Workspace Version** |
+| Vue LS Plugin | via `vue-tsc` / program API | via forked `tsserver` + `@vue/typescript-plugin` |
+
+---
+
+## CI verification
+
+```bash
+# 1. Confirm resolved package
+node -e "console.log(require.resolve('typescript'))"
+
+# 2. Typecheck + require banner (adjust command to your project)
+pnpm exec vue-tsc -b --noEmit 2>&1 | tee /tmp/tsc.log
+grep -F 'TNB ACTIVE' /tmp/tsc.log || { echo 'TNB not active'; exit 1; }
+```
+
+**Linux CI:** The loader supports `bridge.so` / `bridge.dll`, but this repo may
+only ship `bridge.dylib` until you build or publish per-platform binaries. Run
+`npm run build:bridge` on the target OS, or ensure your package artifact includes
+`native/bridge.*` for the runner (see [Platform support](#platform-support)).
+
+Debug slow runs: `TSGO_PROFILE=1` prints a `[tsgo-profile]` timing summary to stderr on process exit (not a `.cpuprofile` file).
+
+---
+
+## Troubleshooting
+
+### No banner appears
+
+| Check | Action |
+|---|---|
+| Override at workspace **root** | Monorepo: `pnpm-workspace.yaml`, not a leaf package |
+| pnpm 11 | Move `package.json` → `pnpm.overrides` to `pnpm-workspace.yaml` → `overrides:` (pnpm 11 no longer reads the `pnpm` field — silently ignored) |
+| `catalog:` pin | Update catalog **and** overrides (see above) |
+| Stale install | `pnpm install` again; clear CI cache if needed |
+| Wrong resolution | `node -e "console.log(require.resolve('typescript'))"` |
+
+### CLI works, editor doesn't (or vice versa)
+
+- **CLI OK, IDE not:** add [Editor / tsserver (tsdk)](#editor--tsserver-tsdk) settings and
+  run **TypeScript: Select TypeScript Version → Use Workspace Version**. Override alone is
+  not enough for the editor.
+- **IDE OK, CLI not:** run `node -e "console.log(require.resolve('typescript'))"` — should
+  point at TNB. Reinstall after changing overrides.
+- CLI and IDE must both resolve the same `node_modules/typescript` (same override at
+  monorepo root).
+
+### Type errors differ from stock TypeScript
+
+TNB is experimental; tsgo parity with JS TypeScript is not 100%. Pin a version, diff
+results, and report gaps. This is expected during early adoption.
+
+### Missing native bridge
+
+Error mentioning `bridge.dylib` / `bridge.so` / `bridge.dll` → run `npm run setup` in
+this repo or ensure published artifacts include your platform.
+
+---
+
+## Platform support
+
+| OS | Native library | Notes |
+|---|---|---|
+| macOS | `native/bridge.dylib` | Primary dev target; may be the only prebuilt binary in a dev clone |
+| Linux | `native/bridge.so` | Build with `npm run build:bridge` on Linux for CI |
+| Windows | `native/bridge.dll` | Supported by loader; build on Windows |
+
+End users of a **published** package need prebuilt binaries per platform. Contributors
+build locally with Go + a C toolchain (`npm run build:bridge`).
+
+---
+
+## Uninstall / rollback
+
+Remove the `typescript` override from `pnpm-workspace.yaml` / `package.json`, reinstall,
+and confirm:
+
+```bash
+pnpm install
+node -e "console.log(require.resolve('typescript'))"   # should be stock typescript@5.x
+```
+
+No source changes in your app are required to roll back.
+
+---
+
+## FAQ
+
+**Do I need to change my code?**  
+No.
+
+**Do I configure `vue-tsc` or ESLint separately?**  
+No. They import `typescript`; one override covers them.
+
+**Is this the same as `@typescript/native-preview`?**  
+No. TNB replaces the full `typescript` package with an in-process Go bridge and Volar/SFC
+integration. `@typescript/native-preview` ships the separate `tsgo` CLI (and preview JS
+API) alongside stock `typescript` — you change scripts to call `tsgo`, not `tsc`.
+
+**How much faster is it?**  
+Depends on project size and shape; large `vue-tsc -b` workloads are the main target.
+Measure on your repo with and without the override.
+
+---
+
+## Developing TNB (contributors)
+
+> End users can skip this section. Consuming a **prebuilt** clone (with `lib/` +
+> `native/bridge.*` already present) does not require Go. Building TNB from source
+> in this repo requires Go, submodules, and `npm run setup`.
+
+### First-time setup
+
+```bash
+git clone --recurse-submodules <repo>
+cd typescript-native-bridge
+npm run setup    # submodules + vendor JS + native bridge + lib/
+```
+
+### All scripts
+
+| Script | Purpose |
+|---|---|
+| `setup` | Full first-time build (everything below) |
+| `build:lib` | **Daily:** overlay → compile → LKG (~6s) |
+| `build:ts` | Cold build (+ `npm install` in typescript submodule) |
+| `build:js` | Compile `typescript-go` native-preview vendor (needed for bridge API types) |
+| `build:bridge` | Rebuild Go `native/bridge.{dylib,so,dll}` |
+| `patch:ts` | Apply `patches/typescript/` to submodule |
+| `patch:tsgo` | Apply `patches/typescript-go/` to submodule |
+| `save-ts-patches` | Save typescript submodule changes → `patches/typescript/` |
+| `save-patches` | Save typescript-go submodule changes → `patches/typescript-go/` |
+| `check:lib-sync` | Verify overlay / submodule / `lib/` are aligned |
+| `check:enums` | Validate TS↔Go enum remapping tables |
+
+### Two patch trees, three artifact families
+
+```
+patches/typescript/overlay/     ← TypeScript-side changes (edit here)
+patches/typescript-go/overlay/  ← Go bridge changes (edit here)
+        ↓ patch + build
+lib/          JS bundles (typescript.js + _tsc.js)
+native/       platform bridge binary
+vendor/       native-preview JS (from build:js)
+```
+
+**TypeScript overlay workflow**
+
+```
+patches/typescript/overlay/
+        ↓  npm run patch:ts   (also run by build:lib)
+typescript/ submodule          ← do not edit by hand
+        ↓  npm run build:lib
+lib/typescript.js              ← tsserver
+lib/_tsc.js                    ← tsc, vue-tsc
+```
+
+Never hand-edit `lib/*.js` or `typescript/src/`. Always rebuild both bundles via
+`build:lib`. Run `npm run check:lib-sync` before committing.
+
+**Go / bridge workflow**
+
+```
+patches/typescript-go/overlay/
+        ↓  npm run patch:tsgo
+typescript-go/ submodule
+        ↓  npm run build:bridge
+native/bridge.*
+```
+
+After editing either submodule working tree: `save-ts-patches` or `save-patches` before commit.
+
+**Changing enums between TS and Go:** run `npm run check:enums`.
+
+---
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
+
+This package is a derivative work of [Microsoft TypeScript](https://github.com/microsoft/TypeScript)
+and [microsoft/typescript-go](https://github.com/microsoft/typescript-go).

package/bin/tsc

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+require('../lib/tsc.js')

package/bin/tsserver

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+require('../lib/tsserver.js')

package/lib/.gitattributes

@@ -0,0 +1 @@
+* text eol=lf