@ts-r.dev/typescript 7.0.1000-alpha.3 → 7.0.1000-alpha.4

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Webb Ventures and the ts-r contributors
+
+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.

package/README.md

@@ -5,12 +5,14 @@ A drop-in for the `typescript` package. Its `tsc` type-checks with
 your own TypeScript on that project, and runs your TypeScript for everything else. Its module API
 (`typescript`, `typescript/unstable/*`) is your TypeScript's.
 
-Your real TypeScript (7.x) stays installed: it is a peer dependency, and the fallback for every
-flag, project and API ts-r doesn't cover.
+Your real TypeScript (7.x) stays installed: it is a peer dependency (or the `typescript-real`
+alias), and the fallback for every flag, project and API ts-r doesn't cover.
 
 ## Install
 
-Either way works; undo it by deleting the line(s).
+Either way works; undo it by deleting the line(s). While ts-r is in alpha, name an exact
+version (below, `7.0.1000-alpha.3`; `npm view @ts-r.dev/typescript dist-tags` lists the
+current ones) or the `next` dist-tag, not a range like `^7`: see [Versions](#versions).
 
 **Next to TypeScript** (point `typescript.tsdk`, scripts or tools at this package):
 
@@ -18,37 +20,64 @@ Either way works; undo it by deleting the line(s).
 // package.json
 "devDependencies": {
   "typescript": "^7.0.0",
-  "@ts-r.dev/typescript": "^7"
+  "@ts-r.dev/typescript": "7.0.1000-alpha.3"
 }
 ```
 
-Run it as `npx -p @ts-r.dev/typescript tsc` or `node_modules/@ts-r.dev/typescript/bin/tsc`, or set
+or `npm install --save-dev typescript@7 @ts-r.dev/typescript@next`. Run it as
+`npx -p @ts-r.dev/typescript tsc` or `node_modules/@ts-r.dev/typescript/bin/tsc`, or set
 `"typescript.tsdk": "node_modules/@ts-r.dev/typescript/lib"`.
 
 **In place of TypeScript** (every tool that runs `tsc` or imports `typescript` gets this package):
 
 ```jsonc
 "devDependencies": {
-  "typescript": "npm:@ts-r.dev/typescript@^7",
+  "typescript": "npm:@ts-r.dev/typescript@next",
   "typescript-real": "npm:typescript@^7.0.0"
 }
 ```
 
-The `typescript-real` alias is how the drop-in finds your TypeScript when it occupies the
-`typescript` name itself.
+(An exact version works too, from the first release after `7.0.1000-alpha.3`: alpha.3 and
+earlier were published with a `typescript` peer range that fails this install with `ERESOLVE`;
+see [Versions](#versions).) The `typescript-real` alias is how the drop-in
+finds your TypeScript when it occupies the `typescript` name itself. Tools that find
+TypeScript by resolving `typescript` from your project, such as `next build`, only use the
+drop-in this way (see [Next.js](#nextjs)).
+
+### Versions
+
+The version is TypeScript's `major.minor`, a patch that encodes the ts-r version (ts-r
+0.1.0 -> `7.0.1000`, 1.2.3 -> `7.0.1002003`) and ts-r's prerelease label: ts-r
+0.1.0-alpha.3 is `7.0.1000-alpha.3`. By semver's rule, which npm follows, a range like `^7` or
+`^7.0.0` never matches a prerelease; a range only matches prereleases of the exact
+`major.minor.patch` it names itself (`^7.0.1000-alpha.3` matches `7.0.1000-alpha.4`, not
+`7.0.2000-alpha.1`). That is deliberate on npm's side (nobody gets an alpha without asking for
+one), and the drop-in keeps the label so its alphas are marked and ordered the same way as
+ts-r's. So during the alpha, pin an exact version or use `next`; `^7` starts to work with
+ts-r's first stable release.
+
+The `typescript` peer dependency is `^7.0.0` plus the drop-in's own version (for
+`7.0.1000-alpha.3`: `^7.0.0 || 7.0.1000-alpha.3`). Installed in place of TypeScript, the
+`typescript` name is the drop-in itself, so npm checks the peer against the drop-in's version;
+without its own version in the range, an alpha fails that check (`ERESOLVE`). Installed next to
+TypeScript, the peer is your TypeScript and must match `^7.0.0`.
 
 ## What `tsc` does
 
 Every run goes through these steps, in order. The first one that applies decides.
 
 1. **`TS_R_TSC=typescript`**: run your TypeScript's `tsc` with the arguments unchanged.
-2. **Flags ts-r-check doesn't support go to your TypeScript.** ts-r-check takes
-   `-p`/`--project <file or dir>`, `--noEmit [true|false]` and `--pretty [true|false]` (names
-   are case-insensitive, like tsc's). Anything else (file names, `--build`, `--watch`,
-   `--declaration`, `--outDir`, `--strict`, `--init`, `--showConfig`, `--listFiles`, ...) runs
-   your `tsc` with the arguments unchanged and prints one line on stderr:
+2. **Flags ts-r-check doesn't support go to your TypeScript.** The drop-in takes
+   `-p`/`--project <file or dir>`, `--noEmit [true|false]`, `--pretty [true|false]`,
+   `--tsBuildInfoFile <file>`, and these emit options when set to `false`: `--declaration`
+   (`-d`), `--declarationMap`, `--emitDeclarationOnly`, `--sourceMap`, `--inlineSourceMap` and
+   `--inlineSources` (option names are case-insensitive, like tsc's). Anything else (file
+   names, `--build`, `--watch`, `--declaration` on its own or `true`, `--outDir`, `--strict`,
+   `--init`, `--listFiles`, ...) runs your `tsc` with the arguments unchanged and prints one line
+   on stderr:
    `@ts-r.dev/typescript: ts-r-check doesn't support --watch; running TypeScript 7.0.2's tsc.`
-   `--version`, `-v`, `--help`, `-h` and `--all` go to your TypeScript without that line.
+   `--version`, `-v`, `--help`, `-h`, `--all` and `--showConfig` go to your TypeScript without
+   that line.
 3. **No tsconfig: your TypeScript.** The project is `-p`'s file (or `<dir>/tsconfig.json`), else
    the nearest `tsconfig.json` from the working directory up. If there is none, your `tsc` runs
    and reports it.
@@ -62,27 +91,32 @@ Every run goes through these steps, in order. The first one that applies decides
 7. **Without your TypeScript there is no parity check**: ts-r-check runs, with a note.
 8. **The parity check decides, per project** (the plan's per-project parity rule, the same one
    `ts-r-lsp` uses):
-   - The first run for a project runs ts-r-check and your `tsc` side by side, both with
-     `-p <tsconfig> --noEmit --pretty false` (ts-r-check also with `--sound=off`), and compares
-     their exit codes and their diagnostics as multisets of whole diagnostics (location, code,
-     message and every chained line).
+   - The first run for a project runs ts-r-check and your `tsc` side by side, both with your
+     `-p` (if you gave one) and your other accepted options (`--tsBuildInfoFile`, the emit
+     options set to `false`) as you gave them, then `--noEmit --pretty false` (ts-r-check also
+     with `--sound=off`), and compares their exit codes and their diagnostics as multisets of
+     whole diagnostics (location, code, message and every chained line).
    - **Match**: this run and later runs use ts-r-check. **Mismatch**: this run and later runs
      use your TypeScript for that project, and a stderr note gives the path of a plain-text
      report listing the diagnostics only one side produced.
    - The result is cached in `<ts-r cache>/typescript/parity/<key>.json` (the cache is
      `$TS_R_CACHE_DIR`, else `$XDG_CACHE_HOME/ts-r`, `%LOCALAPPDATA%\ts-r` or `~/.cache/ts-r`).
      The key covers the tsconfig path, the text of the tsconfig and every config it extends, the
-     nearest lockfile, your TypeScript's version and the ts-r-check version and binary. Editing
-     source files doesn't re-run the check; changing any of those does. Delete the directory to
-     force a re-check.
-   - On that first run, when the output isn't pretty (`--pretty false`, `"pretty": false`, or
-     stdout isn't a terminal), the captured output of the chosen side is printed and its exit
-     code returned, so nothing runs twice. With pretty output, the chosen side runs again with
-     your arguments.
-
-When ts-r-check runs, it gets `-p <tsconfig> --noEmit --sound=off --pretty <true|false>` (your
-`--pretty`, else tsconfig's `"pretty": false`, else whether stdout is a terminal). Its
-output format and exit codes are tsc's: 0 without errors, 1 with errors (no emit happens).
+     nearest lockfile, your TypeScript's version, the ts-r-check version and binary, and the
+     options passed to both checkers (so `tsc` and `tsc --declarationMap false` are checked
+     separately). Editing source files doesn't re-run the check; changing any of those does.
+     Delete the directory to force a re-check.
+   - On that first run, when the output isn't pretty (see below), the captured output of the
+     chosen side is printed and its exit code returned, so nothing runs twice. With pretty
+     output, the chosen side runs again with your arguments.
+
+When ts-r-check runs, it gets your `-p` only if you gave one (without it, ts-r-check finds the
+nearest `tsconfig.json` the way tsc does, and diagnostic paths stay relative to the working
+directory like tsc's), your other accepted options as given, then
+`--noEmit --sound=off --pretty <true|false>`. Pretty output follows tsc 7: your `--pretty`,
+else off when `NO_COLOR` is set (non-empty), else on when `FORCE_COLOR` is set (non-empty),
+else whether stdout is a terminal; like tsc 7, `pretty` in tsconfig is ignored. Its output
+format and exit codes are tsc's: 0 without errors, 1 with errors (no emit happens).
 Diagnostics come sorted by file and position; tsc prints them in program order, so the order can
 differ even when the parity check passed (it compares multisets).
 
@@ -116,6 +150,16 @@ so its output and exit code are exactly its own.
 - Nothing in the API is implemented by ts-r yet, so the "everything goes to your TypeScript"
   part of the parity rule holds for the API at all times.
 
+## Next.js
+
+`next build` type-checks by running the `tsc` of the `typescript` package it resolves from your
+project, so it uses the drop-in when the drop-in is installed in place of TypeScript. Next.js 16
+runs `tsc --showConfig --project <tsconfig> --pretty false` (this goes to your TypeScript), then
+`tsc --project <tsconfig> --noEmit --declarationMap false --emitDeclarationOnly false`, plus
+`--tsBuildInfoFile .next/cache/.tsbuildinfo` for an `incremental` project (Next.js's default
+tsconfig is). The drop-in takes that second command, so the check runs on ts-r-check once the
+parity check passes, and on your TypeScript otherwise.
+
 ## Editors
 
 `typescript.tsdk` pointed at `node_modules/@ts-r.dev/typescript/lib` keeps the editor on your
@@ -126,6 +170,9 @@ applies the same parity rule per project.
 ## Limits
 
 - `tsc --build`, `--watch`, emitting builds and project references always run your TypeScript.
-- `incremental`/`composite` projects checked by ts-r-check don't update `.tsbuildinfo`.
+- For `incremental`/`composite` projects ts-r-check writes a `.tsbuildinfo` in its own format at
+  the path tsc uses (`--tsBuildInfoFile`/`tsBuildInfoFile`, else tsc's default). tsc reads
+  that file as out of date and checks the whole project once, then writes its own; ts-r-check
+  does the same with tsc's, so switching between the two costs one full check each way.
 - tsserver plugins, TypeScript 5/6 as a library (typescript-eslint, ts-morph) need TypeScript
   5/6 installed under its own name, the same as with TypeScript 7 itself.

package/lib/tsc.cjs

@@ -12,7 +12,11 @@ const { OWN, findRealTypeScript, findTsrCheck } = require('./real.cjs');
 
 const PREFIX = '@ts-r.dev/typescript:';
 // Flags that only print something: passed to TypeScript without a note.
-const INFO_FLAGS = new Set(['-v', '--version', '-h', '--help', '--all', '-?']);
+const INFO_FLAGS = new Set(['-v', '--version', '-h', '--help', '--all', '-?', '--showconfig']);
+// Emit options that do nothing when set to `false` under noEmit (Next.js's type check passes
+// `--declarationMap false --emitDeclarationOnly false`). Only the `false` form is taken; any
+// other value goes to TypeScript.
+const EMIT_OFF_FLAGS = new Set(['-d', '--declaration', '--declarationmap', '--emitdeclarationonly', '--sourcemap', '--inlinesourcemap', '--inlinesources']);
 
 function note(msg) {
   if (!process.env.TS_R_TSC_QUIET) process.stderr.write(`${PREFIX} ${msg}\n`);
@@ -22,9 +26,13 @@ function verbose(msg) {
   if (process.env.TS_R_TSC_VERBOSE) process.stderr.write(`${PREFIX} ${msg}\n`);
 }
 
-/** tsc's command line, reduced to what ts-r-check supports. Option names are case-insensitive. */
+/**
+ * tsc's command line, reduced to what ts-r-check supports. Option names are case-insensitive.
+ * `passed` holds the accepted options other than -p, --noEmit and --pretty, as given: both
+ * checkers get them, in the parity run and after it.
+ */
 function parseArgs(argv) {
-  const r = { project: null, noEmit: null, pretty: null, unsupported: [] };
+  const r = { project: null, noEmit: null, pretty: null, passed: [], unsupported: [] };
   for (let i = 0; i < argv.length; i++) {
     const a = argv[i];
     const lower = a.toLowerCase();
@@ -43,6 +51,11 @@ function parseArgs(argv) {
       r.noEmit = bool();
     } else if (lower === '--pretty') {
       r.pretty = bool();
+    } else if (EMIT_OFF_FLAGS.has(lower) && argv[i + 1] === 'false') {
+      r.passed.push(a, argv[++i]);
+    } else if (lower === '--tsbuildinfofile' && i + 1 < argv.length) {
+      // Both checkers write their .tsbuildinfo there (each reads the other's as out of date).
+      r.passed.push(a, argv[++i]);
     } else {
       r.unsupported.push(a);
     }
@@ -161,11 +174,15 @@ function cacheRoot() {
   return path.join(os.homedir(), '.cache', 'ts-r');
 }
 
-/** Parity is cached per tsconfig (and what it extends), lockfile, TypeScript and ts-r-check. */
-function parityKey(config, configFiles, real, tsrCheck) {
+/**
+ * Parity is cached per tsconfig (and what it extends), lockfile, TypeScript, ts-r-check and the
+ * options passed to both checkers.
+ */
+function parityKey(config, configFiles, real, tsrCheck, args) {
   const h = crypto.createHash('sha256');
-  h.update('parity-v1\0');
+  h.update('parity-v2\0');
   h.update(`${config}\0${real.version}\0${OWN.version}\0`);
+  h.update(`${JSON.stringify(checkArgs(args))}\0`);
   try {
     const st = fs.statSync(tsrCheck);
     h.update(`${st.size}\0${st.mtimeMs}\0`);
@@ -246,14 +263,24 @@ function runReal(real, argv, why) {
 }
 
 // `-p` exactly as given (or none: both tools then find the nearest tsconfig the same way), so
-// diagnostic paths come out relative to the working directory just like tsc's.
-function projectArgs(args) {
-  return args.project !== null ? ['-p', args.project] : [];
+// diagnostic paths come out relative to the working directory just like tsc's; then the other
+// accepted options, as given.
+function checkArgs(args) {
+  return [...(args.project !== null ? ['-p', args.project] : []), ...args.passed];
 }
 
-// ts-r-check doesn't read `pretty` from tsconfig, so the effective setting is always passed.
+// The effective setting is always passed, so the parity run and later runs agree on it.
 function tsrArgs(args, pretty) {
-  return [...projectArgs(args), '--noEmit', '--sound=off', '--pretty', String(pretty)];
+  return [...checkArgs(args), '--noEmit', '--sound=off', '--pretty', String(pretty)];
+}
+
+// tsc 7's default for --pretty, as observed: a non-empty NO_COLOR turns it off, else a non-empty
+// FORCE_COLOR turns it on (Next.js sets FORCE_COLOR=1 when its own output is a terminal), else
+// it follows whether stdout is a terminal. tsc 7 ignores `pretty` in tsconfig.
+function defaultPretty(env = process.env, isTTY = process.stdout.isTTY) {
+  if (env.NO_COLOR) return false;
+  if (env.FORCE_COLOR) return true;
+  return Boolean(isTTY);
 }
 
 async function main() {
@@ -278,7 +305,7 @@ async function main() {
   const tsrCheck = findTsrCheck();
   if (!tsrCheck) return runReal(real, argv, `the ts-r-check binary for ${process.platform}-${process.arch} isn't installed`);
   const shownConfig = path.relative(process.cwd(), config) || config;
-  const pretty = args.pretty !== null ? args.pretty : read.options.pretty === false ? false : Boolean(process.stdout.isTTY);
+  const pretty = args.pretty !== null ? args.pretty : defaultPretty();
   if (mode === 'ts-r') return run(tsrCheck, tsrArgs(args, pretty));
   if (!real) {
     note(`TypeScript wasn't found, so ${shownConfig} has no parity check; using ts-r-check.`);
@@ -286,7 +313,7 @@ async function main() {
   }
 
   const dir = path.join(cacheRoot(), 'typescript', 'parity');
-  const key = parityKey(config, read.files, real, tsrCheck);
+  const key = parityKey(config, read.files, real, tsrCheck, args);
   const cacheFile = path.join(dir, `${key}.json`);
   let parity = null;
   try {
@@ -302,7 +329,7 @@ async function main() {
   }
 
   // First run: both checkers, side by side, in tsc's plain format; compare; remember.
-  const plain = [...projectArgs(args), '--noEmit', '--pretty', 'false'];
+  const plain = [...checkArgs(args), '--noEmit', '--pretty', 'false'];
   const t0 = Date.now();
   const [ours, theirs] = await Promise.all([
     capture(tsrCheck, [...plain, '--sound=off']),
@@ -375,6 +402,6 @@ function cli() {
   });
 }
 
-module.exports = { cli, parseArgs, parseJsonc, diagnostics, multisetDiff, readConfig };
+module.exports = { cli, parseArgs, parseJsonc, diagnostics, multisetDiff, readConfig, defaultPretty };
 
 if (require.main === module) cli();

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@ts-r.dev/typescript",
-  "version": "7.0.1000-alpha.3",
+  "version": "7.0.1000-alpha.4",
   "description": "Drop-in for the typescript package: tsc runs ts-r-check where it gives the same results as your TypeScript, and everything else goes to your TypeScript",
-  "license": "MIT OR Apache-2.0",
+  "license": "MIT",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/Webb-Ventures/typescript-rust.git",
@@ -22,7 +22,8 @@
   "files": [
     "bin",
     "lib",
-    "README.md"
+    "README.md",
+    "LICENSE"
   ],
   "exports": {
     ".": {
@@ -79,13 +80,13 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@ts-r.dev/check": "0.1.0-alpha.3"
+    "@ts-r.dev/check": "0.1.0-alpha.4"
   },
   "peerDependencies": {
-    "typescript": "^7.0.0"
+    "typescript": "^7.0.0 || 7.0.1000-alpha.4"
   },
   "ts-r": {
-    "version": "0.1.0-alpha.3",
+    "version": "0.1.0-alpha.4",
     "typescript": "7.0.2"
   }
 }