mirror of
https://github.com/kuhyx/utils.git
synced 2026-11-10 17:47:24 +01:00
Krzysztof kuhy Rudnicki
eaa5683ff1
Matches the Phase 1 design_system pattern the brief points at: own lint config, own tests, own coverage gate enforced in CI. The lint script was declared but unrunnable -- there was no eslint flat config, and the build tsconfig excludes tests (correctly; they must not ship in dist/), so type-aware linting had no project for them. Adds eslint.config.js and a lint-only tsconfig that widens the include without emitting. Running it surfaced one real defect: nth() interpolated a number into a template literal without String(), which the consumers' configs would have flagged. The gate also checks that the committed dist/ matches a fresh build. This is not theoretical -- the check caught the stale dist/ produced by that very String() fix on its first run. A stale dist/ in a tag ships old code to every consumer with no error anywhere, which is the one failure mode this packaging choice introduces. dist/ is excluded from the whitespace hooks: they would "fix" generated output that the next build immediately reverts. CI additionally re-runs the categorical ramp's constraint proof, so the palette cannot regress silently either. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01U4Rj3s7K2qzrLNgJqqPhno
15 lines
503 B
JSON
15 lines
503 B
JSON
{
|
|
// tsconfig.json deliberately excludes tests -- they must not land in the
|
|
// published dist/. Type-aware linting still needs them in a project, so this
|
|
// config widens the include for eslint (and `tsc --noEmit`) only. It emits
|
|
// nothing and clears rootDir, so it cannot affect the shipped build.
|
|
"extends": "./tsconfig.json",
|
|
"compilerOptions": {
|
|
"noEmit": true,
|
|
"rootDir": ".",
|
|
"types": ["vitest/globals", "node"]
|
|
},
|
|
"include": ["src", "*.config.ts"],
|
|
"exclude": []
|
|
}
|