refactor(lint): v0.15 ESLint/TS Quick-Wins — verifizierte Verschärfungen#163
Merged
Conversation
added 2 commits
June 23, 2026 13:32
…le noUncheckedSideEffectImports Verified 0 violations across src + all packages (measured by setting each rule to error and running lint:strict + lint:packages). noUncheckedSideEffectImports likewise 0 errors across root + all package typechecks. - @typescript-eslint/no-shadow: warn -> error (src + packages) - @typescript-eslint/unified-signatures: warn -> error (src + packages) - tsconfig base: noUncheckedSideEffectImports: true
…uires These rules set exactly the value recommendedTypeChecked / stylisticTypeChecked already provide. Verified via `eslint --print-config` that all 14 type-checked defaults stay active as error in BOTH src and packages after removal (behaviour-identical). prefer-ts-expect-error is deprecated (ban-ts-comment with ts-ignore:false covers it); no-var-requires was renamed to no-require-imports in typescript-eslint v6 (dead key). no-floating-promises kept (also set in site/, not redundant there); dot-notation:off kept (documenting pair with no-shadow:off). - 16 redundant @typescript-eslint defaults removed from src + packages blocks - Core prefer-promise-reject-errors removed (preset prefers the TS variant) - dead no-var-requires removed from scripts block - net -33 lines, 0 behaviour change (proven via print-config)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v0.15 — ESLint/TS Quick-Wins (Teil 1: Verschärfungen)
Erster, 0-Risiko-Teil der ESLint-Modernisierung. Alle Änderungen empirisch gemessen (Regel testweise auf
error/Flag aktiv → Fehler gezählt), nicht geschätzt.Detail-Spec (lokal, gitignored):
.workspace/specs/v0.15-hardening/07-eslint-modernization.mdÄnderungen
@typescript-eslint/no-shadowwarn→error(src + packages) — 0 Verstöße gemessen.@typescript-eslint/unified-signatureswarn→error(src + packages) — 0 Verstöße (die per-file-offfürLoader/ParticleSystembleiben).noUncheckedSideEffectImports: true(exojs-config/typescript/base.json) — 0 Fehler über root + alle 5 Pakete.Verifikation (lokale CI-Parität)
lint:strict+lint:packages: 0 neue Fehlertypecheck+ alle 5 Paket-typechecks: grünformat:check: grünKontext + dokumentierte Folge-Schritte
Kernbefund der Analyse: ExoJS ist in den Basis-Regeln bereits strenger als gängige Referenzen; die echte Schwäche sind die ~30 per-Verzeichnis-
off-Blöcke (= Welle 2 / Epic 1, separat). Im Spec geplant als Folge-PRs:no-var-requires+prefer-ts-expect-errorraus (sorgfältig, da sich Werte über Blöcke überschneiden).noUnusedLocals/noUnusedParameters+ Aufräumen von 11 toten Deklarationen.@vitest/eslint-pluginfür Tests.