From 12cf1f8e63c7fd68fee0fd064b9f0a621447bc5f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=81ukasz=20Jerci=C5=84ski?= Date: Sat, 11 Jul 2026 13:43:35 +0200 Subject: [PATCH 1/2] chore: re-render managed files with @j4k/align@1.82.1 --- types/css-modules.d.ts | 18 ------------------ 1 file changed, 18 deletions(-) delete mode 100644 types/css-modules.d.ts diff --git a/types/css-modules.d.ts b/types/css-modules.d.ts deleted file mode 100644 index fbc38f9..0000000 --- a/types/css-modules.d.ts +++ /dev/null @@ -1,18 +0,0 @@ -// Under tsgo build mode the strict base type-checks CSS side-effect imports -// (`import "./styles.css"`), which fail with TS2882 unless an ambient `*.css` -// module is in scope. This shim supplies them for every solution-root repo — -// Next.js apps, but also Vite/React and Tailwind repos that side-effect-import -// CSS. Next.js also ships its own copies (next/types/global.d.ts) via a generated -// `next-env.d.ts`; the overlap is harmless (`skipLibCheck` is on and both -// declarations are type-compatible) and this shim keeps the gate green even -// before `next typegen` runs. -// -// The typed `*.module.css` must come first: tsgo ranks pattern modules by prefix -// length only, both prefixes are empty, so the first-declared wins the tie. A -// leading bare `*.css` would shadow `*.module.css` and collapse every module-CSS -// import to `any` (verified against tsgo 7.0.2). -declare module "*.module.css" { - const classes: Readonly>; - export default classes; -} -declare module "*.css"; From 9d9f174a0bbef808d84279e75fcb4d1557484cac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=81ukasz=20Jerci=C5=84ski?= Date: Sat, 11 Jul 2026 14:08:45 +0200 Subject: [PATCH 2/2] chore: correct README node floor and drop stale knip entry Fix a documentation-vs-code contradiction and a dangling config entry that surfaced during the align re-render review: - README stated Node >= v22.19.0 while package.json engines is >=24.0.0; a Node 22 install would hit EBADENGINE. Align the README to v24.0.0. - knip.json entry still listed the now-deleted types/css-modules.d.ts, leaving a permanent "no matches" configuration hint. Drop it; entry is repo-owned (the aligner only manages $schema/ignore/github-actions). --- README.md | 2 +- knip.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9a714cd..a7ec96d 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ Managing these rules across numerous projects can be tedious. `sync-rules` lets ## Installation -Requires Node.js v22.19.0 or higher. +Requires Node.js v24.0.0 or higher. ```bash npm install -g sync-rules diff --git a/knip.json b/knip.json index 6fd95fc..0ebd5e5 100644 --- a/knip.json +++ b/knip.json @@ -1,5 +1,5 @@ { "$schema": "https://unpkg.com/knip@6/schema.json", - "entry": ["src/cli/main.ts", "types/ts-reset.d.ts", "types/css-modules.d.ts"], + "entry": ["src/cli/main.ts", "types/ts-reset.d.ts"], "project": ["src/**/*.ts", "types/**/*.d.ts"] }