Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
35819
11a24c8e cleanup(linter): refresh workspace-rules-project snapshot for tsconfig.spec.json isolatedModules Follow-up to 069cf3075e which added `isolatedModules: true` to the generated tsconfig.spec.json. Snapshot entry 4 was not refreshed.
by Leosvel Pé...
Succeeded
35819
069cf307 fix(linter): generate workspace-rules-project tsconfig.spec.json with isolatedModules `@typescript-eslint/rule-tester` only exposes its API through an `exports` map (no `main`). Without `isolatedModules: true`, the `module: node16` setting inherited from the project's base `tsconfig.json` triggers ts-jest's TS151002 warning and the generated `.spec.ts` fails to resolve `@typescript-eslint/rule-tester`. Setting `isolatedModules: true` (matching the repo's own `tools/eslint-rules` configuration) ensures the package resolves reliably. Also restores the workspace-rule template's `@typescript-eslint/rule-tester` import for any ESLint v9+ workspace (flat or eslintrc) — typescript-eslint's recommended replacement for the eslintrc-style `RuleTester` API that v9 dropped — instead of relying on `TSESLint.RuleTester`, whose `@typescript-eslint/utils@^8` type definitions are still locked to the eslintrc constructor shape and reject flat-style args at type-check time.
by Leosvel Pé...
Failed
35819
Fix available→
069cf307 fix(linter): generate workspace-rules-project tsconfig.spec.json with isolatedModules `@typescript-eslint/rule-tester` only exposes its API through an `exports` map (no `main`). Without `isolatedModules: true`, the `module: node16` setting inherited from the project's base `tsconfig.json` triggers ts-jest's TS151002 warning and the generated `.spec.ts` fails to resolve `@typescript-eslint/rule-tester`. Setting `isolatedModules: true` (matching the repo's own `tools/eslint-rules` configuration) ensures the package resolves reliably. Also restores the workspace-rule template's `@typescript-eslint/rule-tester` import for any ESLint v9+ workspace (flat or eslintrc) — typescript-eslint's recommended replacement for the eslintrc-style `RuleTester` API that v9 dropped — instead of relying on `TSESLint.RuleTester`, whose `@typescript-eslint/utils@^8` type definitions are still locked to the eslintrc constructor shape and reject flat-style args at type-check time.
by Leosvel Pé...
Failed
35819
Fix available→
3f6e9e45 cleanup(linter): keep @typescript-eslint/utils for the eslintrc rule-test template across ESLint majors `TSESLint.RuleTester` (from `@typescript-eslint/utils`, already installed by `lintWorkspaceRulesProjectGenerator`) just extends `eslint.RuleTester`, so its accepted constructor shape follows the installed ESLint major. The eslintrc rule-test template now branches on `eslintMajor` to emit eslintrc-style args for v8 and flat-style args for v9, while `@typescript-eslint/rule-tester` stays scoped to flat-config workspaces. This avoids requiring v9 + eslintrc workspaces to install an extra dependency.
by Leosvel Pé...
Failed
35819
2288b723 cleanup(linter): refresh workspace-rule snapshots after rule-tester template change The snapshots were captured against the eslintrc-style template and became stale once the generator started emitting the flat-style `@typescript-eslint/rule-tester` template for fresh installs (which now default to ESLint v9).
by Leosvel Pé...
Failed
35819
2d270720 feat(linter): default fresh ESLint installs to v9 across all config shapes Fresh installs (no `eslint` declared) now always pull ESLint v9 regardless of the user's flat-config preference. The eslintrc-shape config files generated when `useFlatConfig(tree)` is false are still honored — v9 loads them through `LegacyESLint` — only the installed package versions move forward. Existing v8 workspaces are untouched because their declared major still routes through `versionMap[8]`.
by Leosvel Pé...