@williamthorsen/tsconfig 0.7.0 → 0.9.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.0";
+export const __readyupVersion = "0.35.1";
 
 
 // .readyup/kits/default.ts

package/.readyup/manifest.json

@@ -53,10 +53,10 @@
       ],
       "name": "default",
       "path": "kits/default.js",
-      "readyupVersion": "0.35.0",
+      "readyupVersion": "0.35.1",
       "source": "kits/default.ts",
       "sourceHash": "f4ec4ffd",
-      "targetHash": "2bcc6e9b"
+      "targetHash": "9949c309"
     }
   ]
 }

package/README.md

@@ -3,13 +3,15 @@
 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.
 
 <!-- section:release-notes -->
-## Release notes — v0.7.0 (2026-08-30)
+## Release notes — v0.9.0 (2026-09-08)
 
 ### 🎉 Features
 
-- Report an include, exclude, or files path outside a tsconfig's directory (#197)
+- 🚨 **Breaking:** Stop exempting vitest from n/no-extraneous-import (#219)
 
-  Adds a `hygiene` checklist to the `@williamthorsen/tsconfig` readiness kit, reporting at `warn` a workspace tsconfig whose effective `include`, `exclude`, or `files` names a path outside the directory holding it, whether that config declared the field itself or inherited it from a base.
+  - 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.
 <!-- /section:release-notes -->
 
 ## Installation
@@ -78,9 +80,9 @@ The base declares none of these:
 
 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.
 
-## Checking your configuration
+## Checking the configuration
 
-This package ships a [ReadyUp](https://www.npmjs.com/package/readyup) kit that checks whether your tsconfigs are wired for the version you have installed. 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:
 
@@ -88,7 +90,7 @@ Run it once:
 pnpm exec rdy run --from npm:@williamthorsen/tsconfig
 ```
 
-Or list it in `.config/readyup.config.ts` to include it whenever you run `rdy run --packages`:
+Or list it in `.config/readyup.config.ts` to include it in every `rdy run --packages`:
 
 ```ts
 import { defineRdyConfig } from 'readyup';
@@ -105,10 +107,10 @@ 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.
 - **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 you extend rather than from a constant compiled into the kit.
+- **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.
 
-The kit runs at the version resolved from your `node_modules`, so it reports whether your configuration matches that version. It never reports whether that version is current.
+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.
 
 ## License
 

package/package.json

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

package/tsconfig.base.json

@@ -28,6 +28,9 @@
 
     // 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.
+    "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.
     "lib": ["ES2025", "ESNext.Disposable"],