@williamthorsen/tsconfig 0.4.0 → 0.5.0

package/.readyup/kits/default.js

@@ -1,6 +1,6 @@
 /** @noformat — @generated. Do not edit. Compiled by rdy. */
 /* eslint-disable */
-export const __readyupVersion = "0.25.0";
+export const __readyupVersion = "0.27.0";
 
 
 // .readyup/kits/default.ts

package/.readyup/manifest.json

@@ -9,10 +9,10 @@
       "description": "Adoption and alignment checks for a project consuming @williamthorsen/tsconfig",
       "name": "default",
       "path": "kits/default.js",
-      "readyupVersion": "0.25.0",
+      "readyupVersion": "0.27.0",
       "source": "kits/default.ts",
       "sourceHash": "4d0a555c",
-      "targetHash": "4c59a48d"
+      "targetHash": "c478ceff"
     }
   ]
 }

package/README.md

@@ -3,13 +3,19 @@
 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.4.0 (2026-08-09)
+## Release notes — v0.5.0 (2026-08-11)
 
 ### 🎉 Features
 
-- Add a bundled readyup kit that checks tsconfig adoption and alignment (#152)
+- 🚨 **Breaking:** Require author, engines, and publish metadata in package.json (#162)
 
-  Adds a readiness check to `@williamthorsen/tsconfig` that reports, package by package, whether a repo has adopted the base config and stayed aligned with it. A package that extends a framework's own base is reported as having opted out. The Node floor is the only finding that fails the check; the rest is advisory. The check is run with `pnpm exec rdy run --from npm:@williamthorsen/tsconfig`.
+  Adds six `package-json` rules to `@williamthorsen/eslint-config-typescript` and removes three overrides that suppressed rules the plugin's `recommended` preset supplies. Every `package.json` must now declare `author` and `engines` and carry no empty field; one that publishes must also declare `bugs`, `homepage`, `keywords`, `repository`, and `sideEffects`, and may not take a dependency on a local path. `specify-peers-locally` is the only rule the config still disables.
+
+### 🐛 Bug fixes
+
+- Accept a source-path import in the kit's extends check (#155)
+
+  Fixes an issue where the readiness check bundled with `@williamthorsen/eslint-config-typescript` reported that this repo's root ESLint config did not extend the package. The kit now accepts that an import via the workspace path is equivalent.
 <!-- /section:release-notes -->
 
 ## Installation

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@williamthorsen/tsconfig",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Shared TypeScript base config for Node-only projects",
   "keywords": [
     "tsconfig",
@@ -17,6 +17,7 @@
   },
   "license": "ISC",
   "author": "William Thorsen <william@thorsen.dev> (https://github.com/williamthorsen)",
+  "sideEffects": false,
   "type": "module",
   "exports": {
     "./package.json": "./package.json",
@@ -30,7 +31,7 @@
   "devDependencies": {
     "@tsconfig/strictest": "2.0.8",
     "esbuild": "0.28.1",
-    "readyup": "0.25.0"
+    "readyup": "0.27.0"
   },
   "engines": {
     "node": ">=24"

package/tsconfig.base.json

@@ -31,7 +31,7 @@
     // 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"],
-    // Default is `ES2022` with `Bundler` resolution — wrong for published Node packages.
+    // Default is `ES2022` with `Bundler` resolution: wrong for published Node packages.
     "module": "NodeNext",
     // Files with no import or export would otherwise be scripts sharing global scope.
     "moduleDetection": "force",