Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
34026
08dcdc18 fix(linter): handle variable references in replaceOverride The migration generator (@nx/plugin:migration) fails when the project's ESLint flat config contains variable references in property values, such as: `plugins: { 'package-json': pluginPackageJson }` This happens because `replaceOverride` uses `parseTextToJson` to parse the config, which fails for non-JSON-serializable JavaScript expressions. The migration generator should work correctly even when the ESLint config contains variable references. The fix applies the same approach used in PR #33548 for `hasOverride`: using AST-based property extraction instead of JSON parsing. Fixes #34010 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2 months ago by jaysoo
Failed
34026
187a1aeb fix(linter): handle variable references in replaceOverride The migration generator (@nx/plugin:migration) fails when the project's ESLint flat config contains variable references in property values, such as: `plugins: { 'package-json': pluginPackageJson }` This happens because `replaceOverride` uses `parseTextToJson` to parse the config, which fails for non-JSON-serializable JavaScript expressions. The migration generator should work correctly even when the ESLint config contains variable references. The fix applies the same approach used in PR #33548 for `hasOverride`: using AST-based property extraction instead of JSON parsing. Fixes #34010 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2 months ago by jaysoo
Succeeded
34026
b1925635 fix(linter): handle variable references in replaceOverride The migration generator (@nx/plugin:migration) fails when the project's ESLint flat config contains variable references in property values, such as: `plugins: { 'package-json': pluginPackageJson }` This happens because `replaceOverride` uses `parseTextToJson` to parse the config, which fails for non-JSON-serializable JavaScript expressions. The migration generator should work correctly even when the ESLint config contains variable references. The fix applies the same approach used in PR #33548 for `hasOverride`: using AST-based property extraction instead of JSON parsing. Fixes #34010 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2 months ago by jaysoo
Failed
34026
Environment issue→
28db3c5b fix(linter): handle variable references in replaceOverride The migration generator (@nx/plugin:migration) fails when the project's ESLint flat config contains variable references in property values, such as: `plugins: { 'package-json': pluginPackageJson }` This happens because `replaceOverride` uses `parseTextToJson` to parse the config, which fails for non-JSON-serializable JavaScript expressions. The migration generator should work correctly even when the ESLint config contains variable references. The fix applies the same approach used in PR #33548 for `hasOverride`: using AST-based property extraction instead of JSON parsing. Fixes #34010 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2 months ago by jaysoo
Failed
34026
0fc24a70 fix(linter): handle variable references in replaceOverride The migration generator (@nx/plugin:migration) fails when the project's ESLint flat config contains variable references in property values, such as: `plugins: { 'package-json': pluginPackageJson }` This happens because `replaceOverride` uses `parseTextToJson` to parse the config, which fails for non-JSON-serializable JavaScript expressions. The migration generator should work correctly even when the ESLint config contains variable references. The fix applies the same approach used in PR #33548 for `hasOverride`: using AST-based property extraction instead of JSON parsing. Fixes #34010 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3 months ago by jaysoo
Canceled
34026
5c330220 fix(linter): handle variable references in replaceOverride The migration generator (@nx/plugin:migration) fails when the project's ESLint flat config contains variable references in property values, such as: `plugins: { 'package-json': pluginPackageJson }` This happens because `replaceOverride` uses `parseTextToJson` to parse the config, which fails for non-JSON-serializable JavaScript expressions. The migration generator should work correctly even when the ESLint config contains variable references. The fix applies the same approach used in PR #33548 for `hasOverride`: using AST-based property extraction instead of JSON parsing. Fixes #34010 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3 months ago by jaysoo