@williamthorsen/tsconfig 0.9.0 → 0.10.0

package/.readyup/kits/default.js

@@ -1,6 +1,6 @@
 /** @noformat -- @generated. Do not edit. Compiled by rdy. */
 /* eslint-disable */
-export const __readyupVersion = "0.35.1";
+export const __readyupVersion = "0.38.0";
 
 
 // .readyup/kits/default.ts
@@ -193,10 +193,10 @@ var default_default = defineRdyKit({
           fix: `Extend ${BASE_SPECIFIER} from each tsconfig named above, and declare ${PACKAGE_NAME} as a devDependency of each package that names it but cannot resolve it. Adoption: ${ADOPTION_URL}`
         },
         {
-          name: "No tsconfig re-declares an option the base already supplies",
+          name: "No tsconfig re-declares an option that the base already supplies",
           severity: "recommend",
           check: noRedundantOptions,
-          fix: "Delete each option named above: the base already supplies it with the same value"
+          fix: "Delete each option named above: The base already supplies it with the same value"
         }
       ]
     },
@@ -207,14 +207,14 @@ var default_default = defineRdyKit({
           name: `No tsconfig declares an ES year other than the one ${PACKAGE_NAME} sets`,
           skip: skipUnlessBaseEsYearKnown,
           check: everyEsYearMatchesTheBase,
-          fix: "Delete the target or lib declaration named above, so the ES year the base sets applies"
+          fix: "Delete the target or lib declaration named above, so that the ES year set by the base applies"
         },
         {
           name: "The declared Node floor supports the base's ES year",
           severity: "error",
           skip: skipUnlessNodeFloorComparable,
           check: nodeFloorSupportsBaseEsYear,
-          fix: "Raise engines.node to a major implementing the base's ES year: below it, code that typechecks fails at runtime"
+          fix: "Raise engines.node to a major implementing the base's ES year: Below it, code that typechecks fails at runtime"
         }
       ]
     },
@@ -225,7 +225,7 @@ var default_default = defineRdyKit({
           name: "No tsconfig's include, exclude, or files names a path outside its own directory",
           skip: skipUnlessSomeTsconfigWasFound,
           check: noEscapingPaths,
-          fix: "Declare the field named above in the config that owns the directory, listing every path it needs, since a local declaration replaces the inherited one rather than merging and discards the default exclude of node_modules, bower_components, jspm_packages, and outDir; or prefix each path in the config being extended with ${configDir}, which resolves to the consuming config's directory"
+          fix: "Declare the field named above in the config that owns the directory, listing every path that it needs, since a local declaration replaces the inherited one rather than merging and discards the default exclude of node_modules, bower_components, jspm_packages, and outDir; or prefix each path in the config being extended with ${configDir}, which resolves to the consuming config's directory"
         }
       ]
     }

package/.readyup/manifest.json

@@ -11,52 +11,52 @@
       "esbuildVersion": "0.28.2",
       "inputs": [
         {
-          "hash": "f4ec4ffd",
+          "hash": "d1952ca5",
           "kind": "module",
           "path": "kits/default.ts"
         },
         {
-          "hash": "7e083072",
+          "hash": "cee0fa23",
           "kind": "module",
           "path": "../src/readiness/base-chain.ts"
         },
         {
-          "hash": "86555b6e",
+          "hash": "4f053be6",
           "kind": "module",
           "path": "../src/readiness/classifyChain.ts"
         },
         {
-          "hash": "723d4694",
+          "hash": "4861e1ce",
           "kind": "module",
           "path": "../src/readiness/es-year.ts"
         },
         {
-          "hash": "bfbb0002",
+          "hash": "7e81b592",
           "kind": "module",
           "path": "../src/readiness/findEscapingPaths.ts"
         },
         {
-          "hash": "acd6ba2b",
+          "hash": "b84db6a6",
           "kind": "module",
           "path": "../src/readiness/findRedundantOptions.ts"
         },
         {
-          "hash": "30178e5c",
+          "hash": "d53de60d",
           "kind": "module",
           "path": "../src/readiness/listSearchDirs.ts"
         },
         {
-          "hash": "31b0fbf5",
+          "hash": "ecb17b24",
           "kind": "module",
           "path": "../src/readiness/node-floor.ts"
         }
       ],
       "name": "default",
       "path": "kits/default.js",
-      "readyupVersion": "0.35.1",
+      "readyupVersion": "0.38.0",
       "source": "kits/default.ts",
-      "sourceHash": "f4ec4ffd",
-      "targetHash": "9949c309"
+      "sourceHash": "d1952ca5",
+      "targetHash": "db184a57"
     }
   ]
 }

package/README.md

@@ -1,17 +1,13 @@
 # @williamthorsen/tsconfig
 
-Shared TypeScript base config for Node-only projects. Inlines the settings of [`@tsconfig/strictest`](https://www.npmjs.com/package/@tsconfig/strictest) and adds the Node and build options it leaves out, so a consuming repo declares only what is genuinely its own.
+Shared TypeScript base config for Node-only projects. Inlines the settings of [`@tsconfig/strictest`](https://www.npmjs.com/package/@tsconfig/strictest) and adds the Node and build options that it leaves out, so a consuming repo declares only what is genuinely its own.
 
 <!-- section:release-notes -->
-## Release notes — v0.9.0 (2026-09-08)
+## Release notes — v0.10.0 (2026-09-29)
 
 ### 🎉 Features
 
-- 🚨 **Breaking:** Stop exempting vitest from n/no-extraneous-import (#219)
-
-  - Removes the `allowModules: ['vitest']` option from `n/no-extraneous-import`, so the rule now reports `vitest` in any workspace whose own `package.json` does not declare it.
-
-  Migration: Declare `vitest` in the `devDependencies` of every workspace that imports it; in a pnpm workspace, a catalog entry (`"vitest": "catalog:"`) declares it without repeating the version. To keep the old behavior instead, set `'n/no-extraneous-import': ['error', { allowModules: ['vitest'] }]` in the consuming config's own `rules` block.
+- Rewords the messages that the package's ReadyUp kit reports: The redundant-option check is now named "No tsconfig re-declares an option that the base already supplies", and the fix hints for the redundant-option, ES-year, Node-floor, and escaping-path checks are reworded. (#250)
 <!-- /section:release-notes -->
 
 ## Installation
@@ -34,7 +30,7 @@ pnpm add -D @williamthorsen/tsconfig
 
 ## Adopting the base
 
-Extend the base from every tsconfig in the repo, not from the root alone. A workspace config reaches it either directly or through a config that does:
+Extend the base from every tsconfig in the repo, not from the root alone. A workspace config extends it either directly or through a config that does:
 
 ```jsonc
 // packages/api/tsconfig.json
@@ -44,9 +40,9 @@ Extend the base from every tsconfig in the repo, not from the root alone. A work
 }
 ```
 
-Every package whose tsconfig names the base by package specifier must also declare it as a devDependency: TypeScript resolves `extends` from the directory of the config that declares it, so a workspace naming a package it does not depend on resolves nothing.
+Every package whose tsconfig names the base by package specifier must also declare it as a devDependency: TypeScript resolves `extends` from the directory of the config that declares it, so a workspace naming a package on which it does not depend resolves nothing.
 
-Once the base is in the chain, delete the options it already supplies with the same value. The inherited value applies either way, and the copy left behind stops tracking the base the next time it changes. An option set to a _different_ value is an override and stays.
+Once the base is in the chain, delete the options that it already supplies with the same value. The inherited value applies either way, and the copy left behind stops tracking the base the next time it changes. An option set to a _different_ value is an override and stays.
 
 A package that extends a framework base such as `astro/tsconfigs/base` or `@tsconfig/svelte` has opted out of this one, which is a supported choice.
 
@@ -64,7 +60,7 @@ Everything `@tsconfig/strictest` sets, plus the Node and build options it omits:
 | `removeComments`             | `true`                            |
 | `target`                     | `"ES2025"`                        |
 
-`target` and `lib` are pinned to a Node 24 floor. `ESNext.Disposable` supplies the explicit-resource-management declarations (`using`, `Disposable`, `DisposableStack`), which Node 24 implements and no numbered lib yet carries.
+`target` and `lib` are pinned to a Node 24 floor. `ESNext.Disposable` supplies the explicit-resource-management declarations (`using`, `Disposable`, `DisposableStack`), which Node 24 implements but the numbered libs do not yet include.
 
 ## What the consumer owns
 
@@ -78,11 +74,11 @@ The base declares none of these:
 
 ## Emitting
 
-The base sets `noEmit: true`, on the assumption that a separate build step owns emit. A consumer that builds with this config directly must override `noEmit` and, if it keeps `allowImportingTsExtensions`, pair that with `rewriteRelativeImportExtensions` so `./foo.ts` specifiers survive the rewrite.
+The base sets `noEmit: true`, on the assumption that a separate build step owns emit. A consumer that builds with this config directly must override `noEmit` and, if it keeps `allowImportingTsExtensions`, pair that with `rewriteRelativeImportExtensions` so that `./foo.ts` specifiers survive the rewrite.
 
 ## Checking the configuration
 
-This package ships a [ReadyUp](https://www.npmjs.com/package/readyup) kit that checks whether the workspace tsconfigs are wired for the installed version. It is a migration aid rather than a CI gate: only a Node floor too old to run the base's ES year is reported as an error, and everything else caps at a warning.
+This package ships a [ReadyUp](https://www.npmjs.com/package/readyup) kit that checks whether the workspace tsconfigs are wired for the installed version. It is a migration aid rather than a CI gate: Only a Node floor too old to run the base's ES year is reported as an error, and everything else caps at a warning.
 
 Run it once:
 
@@ -100,15 +96,15 @@ export default defineRdyConfig({
 });
 ```
 
-The `readyup >=0.33.0` optional peer names the version the kit is developed and tested against. Below 0.33.0, readyup does not report the repo root among a monorepo's workspaces, so the kit supplies the root itself and sweeps every member package alongside it.
+The `readyup >=0.33.0` optional peer names the version against which the kit is developed and tested. Below 0.33.0, readyup does not report the repo root among a monorepo's workspaces, so the kit supplies the root itself and sweeps every member package alongside it.
 
 The kit walks each workspace tsconfig's `extends` chain and reports five things:
 
 - **Adoption**: a tsconfig reaching neither this base nor a framework base. A tsconfig naming this base through a specifier that does not resolve is reported separately, as declared but not installed.
-- **Re-declaration**: an option restated with the base's own value. A key that a framework base in the same chain also declares is exempt, since restating it is how a config wins against that base.
+- **Re-declaration**: an option restated with the base's own value. A key that a framework base in the same chain also declares is exempt, since restating it is how a config overrides that base.
 - **Escaping paths**: an `include`, `exclude`, or `files` path resolving outside the directory that holds the tsconfig. A config that is extended hands these fields down resolved against its own directory, so a package inheriting them is governed by paths pointing outside itself; the remedy is a complete local declaration, or `${configDir}` in the config being extended.
 - **ES year**: a `target` or `lib` declaring a year other than the base's, read from the base that the tsconfig extends rather than from a constant compiled into the kit.
-- **Node floor**: an `engines.node` below the major that implements that ES year. This is the one failure `tsc` cannot surface on its own, which is why it alone is an error.
+- **Node floor**: an `engines.node` below the major that implements that ES year. This is the one failure that `tsc` cannot report on its own, which is why it alone is an error.
 
 The kit runs at the version resolved from the project's `node_modules`, so it reports whether the configuration matches that version. It never reports whether that version is current.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@williamthorsen/tsconfig",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "description": "Shared TypeScript base config for Node-only projects",
   "keywords": [
     "tsconfig",
@@ -31,7 +31,7 @@
   "devDependencies": {
     "@tsconfig/strictest": "2.0.8",
     "esbuild": "0.28.2",
-    "readyup": "0.35.1",
+    "readyup": "0.38.0",
     "vitest": "4.1.11"
   },
   "peerDependencies": {

package/tsconfig.base.json

@@ -1,8 +1,8 @@
-// Base TSConfig for Node-only TypeScript: `@tsconfig/strictest` plus the Node/build options it omits.
+// Base TSConfig for Node-only TypeScript: `@tsconfig/strictest` plus the Node/build options that it omits.
 // Consumers set `types`, `paths`, `jsx`, and `include`. Node 24 floor.
 //
 // Every Node/build setting deviates from a TypeScript default; a comment says why it can't be dropped.
-// The inlined strictest settings carry no such comments: their rationale belongs to upstream.
+// The inlined strictest settings have no such comments: Their rationale belongs to upstream.
 {
   "$schema": "https://json.schemastore.org/tsconfig",
   "compilerOptions": {
@@ -28,11 +28,11 @@
 
     // Permit `./foo.ts` specifiers; the build step rewrites them on emit.
     "allowImportingTsExtensions": true,
-    // The option TypeScript requires alongside the one above once a build clears `noEmit` and emits with
-    // `tsc`, which rewrites the specifier's extension in output and declarations.
+    // Required alongside `allowImportingTsExtensions` once a build clears `noEmit` and emits with `tsc`,
+    // which then rewrites the specifier's extension in output and declarations.
     "rewriteRelativeImportExtensions": true,
     // Without this, `lib` follows `target` into the `.full` variant, admitting DOM globals.
-    // `ESNext.Disposable` carries the explicit-resource-management declarations; no numbered lib has them.
+    // `ESNext.Disposable` contains the explicit-resource-management declarations; no numbered lib has them.
     "lib": ["ES2025", "ESNext.Disposable"],
     // Default is `ES2022` with `Bundler` resolution: wrong for published Node packages.
     "module": "NodeNext",
@@ -42,6 +42,7 @@
     "noEmit": true,
     // Inert until a build step clears `noEmit`; keeps published output comment-free.
     "removeComments": true,
+    // Default is the latest ES year that the installed TypeScript knows; pin the year that the Node floor implements.
     "target": "ES2025",
   },
 }