INITIAL COMMIT

Author: ycmjason

.gitattributes

@@ -0,0 +1,3 @@
+/.yarn/**            linguist-vendored
+/.yarn/releases/*    binary
+/.yarn/plugins/**/*  binary

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: ycmjason

.github/workflows/cd.yml

@@ -0,0 +1,35 @@
+name: Publish
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+
+    permissions:
+      contents: read
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: 'yarn'
+          registry-url: "https://registry.npmjs.org"
+
+      - name: Install dependencies
+        run: yarn install --immutable
+
+      - run: yarn build
+
+      - name: Publish to npm
+        run: bash ./scripts/build-and-publish.bash
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  ci:
+    name: Build, Lint, Format, TypeCheck and Test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: 'yarn'
+      - name: Install dependencies
+        run: yarn install --immutable
+
+      - name: Build
+        run: yarn build
+
+      - name: Lint and Formating
+        run: yarn check
+
+      - name: Typecheck
+        run: yarn typecheck
+
+      - name: Test
+        run: yarn test

.gitignore

@@ -0,0 +1,18 @@
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/sdks
+!.yarn/versions
+
+# Swap the comments on the following lines if you wish to use zero-installs
+# In that case, don't forget to run `yarn config set enableGlobalCache false`!
+# Documentation here: https://yarnpkg.com/features/caching#zero-installs
+
+#!.yarn/cache
+.pnp.*
+
+dist
+
+node_modules
+!examples/**/node_modules

.vscode/settings.json

@@ -0,0 +1,8 @@
+{
+  "typescript.tsdk": "node_modules/typescript/lib",
+  "search.exclude": {
+    "node_modules": true,
+    "dist": true,
+    ".yarn": true
+  }
+}

.yarn/releases/yarn-4.9.1.cjs

@@ -0,0 +1,3 @@
+yarnPath: .yarn/releases/yarn-4.9.1.cjs
+
+nodeLinker: node-modules

.yarnrc.yml

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 YCM Jason
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

LICENSE

@@ -0,0 +1,131 @@
+# `@ts-migrating` — Progressively Upgrade `tsconfig.json`
+
+🚀 **TypeScript keeps evolving — and your `tsconfig` should too.**
+
+But upgrading often breaks existing code, and fixing all errors at once is unrealistic.
+
+**`@ts-migrating`** helps your team migrate to a desired `tsconfig` gradually and safely.
+
+> I chose `@ts-migrating` (rather than `@ts-migration`) to better reflect the plugin’s progressive and incremental philosophy.
+
+## 🤖 How does this work?
+
+`@ts-migrating` is a TypeScript plugin that lets you **enable your target tsconfig during development** (in IDEs or editors that use the [TypeScript Language Service](https://github.com/microsoft/typescript/wiki/Using-the-Language-Service-API)) and in CI — **without affecting `tsc` or your production build**.
+
+The philosophy behind the plugin follows three simple steps:
+
+1. 🛑 **Prevention**
+
+   * Errors from your target config are surfaced during development and in CI.
+   * This ensures no new violations are introduced into the codebase.
+
+2. 🔧 **Reduction**
+
+   * Lines marked with `@ts-migrating` are temporarily suppressed.
+   * Developers can progressively fix these lines, reducing violations over time.
+
+3. ✅ **Migration**
+
+   * Once all violations are fixed, no `@ts-migrating` directives remain.
+   * At this point, you're ready to fully adopt the new tsconfig — and the plugin has served its purpose.
+
+## 📚 Overview
+
+`@ts-migrating` consists of two parts:
+
+1. 🔌 **[TypeScript Language Service Plugin](https://github.com/microsoft/TypeScript/wiki/Writing-a-Language-Service-Plugin)**
+
+   * Enables IDEs to show errors from the `tsconfig` you're migrating to.
+   * Suppresses errors on lines marked with `@ts-migrating`.
+
+2. 🖥️ **Standalone CLI: `ts-migrating`**
+
+   * `ts-migrating check`
+
+     * Run `@ts-migrating`-aware type checking using your new `tsconfig`.
+   * `ts-migrating annotate`
+
+     * Automatically mark all errors caused by your new `tsconfig` with `@ts-migrating`.
+     * ⚠️ Run this with a clean git state!!! This script will automatically add the `@ts-migrating` directive above every new TypeScript error introduced by your new `tsconfig`. There are edge cases where this will break the code, please review the changes carefully. It is recommended to run your formatter and linter afterwards.
+
+## 🎪 Examples
+
+* [Migrating to `noUncheckedIndexedAccess`](./examples/no-unchecked-indexed-access-migration/src/index.ts):
+
+  | Without `@ts-migrating` | With `@ts-migrating` |
+  | ----------------------- | -------------------- |
+  | ![Migrating to noUncheckedIndexedAccess](./assets/ts-migrating-no-unchecked-indexed-access.png)  | ![Migrating to noUncheckedIndexedAccess marked](./assets/ts-migrating-no-unchecked-indexed-access-marked.png)  |
+
+* [Migrating to `noUncheckedIndexAccess`](./examples/erasable-syntax-only-migration/src/index.ts)
+* [Migrating to `erasableSyntaxOnly`](./examples/erasable-syntax-only-migration/src/index.ts)
+
+## 📦 Install and Setup
+
+This project does **NOT** require any IDE extensions. It relies purely on TypeScript's own Language Service, so it works on most IDEs and editors that support TypeScript (e.g., VSCode, WebStorm).
+
+To install:
+
+```bash
+cd my-cool-project
+npm install -D ts-migrating
+```
+
+In your existing `tsconfig.json`, add the plugin:
+
+```jsonc
+{
+  // ...
+  "compilerOptions": {
+    // ...
+    "plugins": [
+      {
+        "name": "ts-migrating",
+        "compilerOptions": {
+          // ... put the compiler options you wish to migrate to, for example:
+          "strict": true
+        }
+      }
+    ]
+    // ...
+  }
+  // ...
+}
+```
+
+ℹ️ *Note: `plugins` only affect the TypeScript Language Service (used by IDEs). They do **not** impact `tsc` or your build.*
+
+🎉 Your codebase is now ready!
+
+### ✅ Verify the Setup
+
+#### 🧑‍💻 In your IDE
+
+* Restart the IDE, or just the TS server.
+* Confirm that type errors now reflect the new `compilerOptions`. For example, when migrating to strict mode, verify that strict-specific errors appear.
+* Add `// @ts-migrating` before a line with an error — the error should disappear in the IDE.
+
+#### 🖥 In the terminal
+
+* Run:
+
+  ```bash
+  npx ts-migrating check
+  ```
+
+  You should see errors from the new config, excluding those marked with `@ts-migrating`.
+
+### ✨ Optional Next Steps
+
+* Run `npx ts-migrating annotate` to automatically annotate newly introduced errors with `// @ts-migrating`.
+* Replace your CI type-check step with `npx ts-migrating check` to prevent unreviewed errors from slipping through.
+
+## 📣 Shoutout
+
+This project wouldn't be possible without inspiration from:
+
+* [allegro/typescript-strict-plugin](https://github.com/allegro/typescript-strict-plugin):
+  Especially for revealing the undocumented [`updateFromProject` option](https://github.com/allegro/typescript-strict-plugin/blob/master/src/plugin/utils.ts#L28-L32) which helped fix a critical issue with the standalone script. [You can find out more here](./src/plugin/mod.ts#L31)).
+
+## 👤 Author
+
+YCM Jason