Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
master
aca93cc9 fix(core): bump axios to 1.13.5 to resolve CVE-2026-25639 (#35148) ## Current Behavior The `nx`, `create-nx-workspace`, and `nx-dev` packages pin `axios` at version `1.12.0`, which has a known security vulnerability ([CVE-2026-25639](https://github.com/advisories/GHSA-43fc-jf86-j433)). ## Expected Behavior Axios is pinned at `1.13.5`, which includes the fix for CVE-2026-25639, eliminating the security vulnerability. ## Related Issue(s) Fixes #35145
16 days ago by Robert Sid...
Failed
35148
Flaky task→
20b637ab fix(core): bump axios to 1.13.5 to resolve CVE-2026-25639 Fixes #35145
16 days ago by Robert Sid...
Failed
35148
Flaky task→
20b637ab fix(core): bump axios to 1.13.5 to resolve CVE-2026-25639 Fixes #35145
16 days ago by Robert Sid...
Succeeded
master
63a8f27e fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE (#35028) ## Current Behavior `@nx/webpack` depends on `postcss-loader@^6.1.1`, which pulls in `cosmiconfig@7` → `yaml@1.x`. The `yaml@1.x` package has a known stack overflow vulnerability ([GHSA-48c2-rrv3-qjmp](https://github.com/advisories/GHSA-48c2-rrv3-qjmp)). ## Expected Behavior By bumping `postcss-loader` to `^8.2.1`, the transitive dependency chain is eliminated entirely — `postcss-loader@8` uses `cosmiconfig@9`, which no longer depends on `yaml` at all. This is a cleaner fix than applying a `pnpm.overrides` workaround. The upgrade is safe because: - `postcss-loader@8` peer deps (`postcss ^7||^8`, `webpack ^5`) are unchanged - The `implementation` option and function-based `postcssOptions` API used by `@nx/webpack` are fully supported in v8 - Nx already requires Node 18+, matching postcss-loader@8's engine requirement ## Related Issue(s) Fixes #35025
18 days ago by Robert Sid...
Succeeded
master
63a8f27e fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE (#35028) ## Current Behavior `@nx/webpack` depends on `postcss-loader@^6.1.1`, which pulls in `cosmiconfig@7` → `yaml@1.x`. The `yaml@1.x` package has a known stack overflow vulnerability ([GHSA-48c2-rrv3-qjmp](https://github.com/advisories/GHSA-48c2-rrv3-qjmp)). ## Expected Behavior By bumping `postcss-loader` to `^8.2.1`, the transitive dependency chain is eliminated entirely — `postcss-loader@8` uses `cosmiconfig@9`, which no longer depends on `yaml` at all. This is a cleaner fix than applying a `pnpm.overrides` workaround. The upgrade is safe because: - `postcss-loader@8` peer deps (`postcss ^7||^8`, `webpack ^5`) are unchanged - The `implementation` option and function-based `postcssOptions` API used by `@nx/webpack` are fully supported in v8 - Nx already requires Node 18+, matching postcss-loader@8's engine requirement ## Related Issue(s) Fixes #35025
18 days ago by Robert Sid...
Succeeded
master
63a8f27e fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE (#35028) ## Current Behavior `@nx/webpack` depends on `postcss-loader@^6.1.1`, which pulls in `cosmiconfig@7` → `yaml@1.x`. The `yaml@1.x` package has a known stack overflow vulnerability ([GHSA-48c2-rrv3-qjmp](https://github.com/advisories/GHSA-48c2-rrv3-qjmp)). ## Expected Behavior By bumping `postcss-loader` to `^8.2.1`, the transitive dependency chain is eliminated entirely — `postcss-loader@8` uses `cosmiconfig@9`, which no longer depends on `yaml` at all. This is a cleaner fix than applying a `pnpm.overrides` workaround. The upgrade is safe because: - `postcss-loader@8` peer deps (`postcss ^7||^8`, `webpack ^5`) are unchanged - The `implementation` option and function-based `postcssOptions` API used by `@nx/webpack` are fully supported in v8 - Nx already requires Node 18+, matching postcss-loader@8's engine requirement ## Related Issue(s) Fixes #35025
18 days ago by Robert Sid...
Succeeded
master
63a8f27e fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE (#35028) ## Current Behavior `@nx/webpack` depends on `postcss-loader@^6.1.1`, which pulls in `cosmiconfig@7` → `yaml@1.x`. The `yaml@1.x` package has a known stack overflow vulnerability ([GHSA-48c2-rrv3-qjmp](https://github.com/advisories/GHSA-48c2-rrv3-qjmp)). ## Expected Behavior By bumping `postcss-loader` to `^8.2.1`, the transitive dependency chain is eliminated entirely — `postcss-loader@8` uses `cosmiconfig@9`, which no longer depends on `yaml` at all. This is a cleaner fix than applying a `pnpm.overrides` workaround. The upgrade is safe because: - `postcss-loader@8` peer deps (`postcss ^7||^8`, `webpack ^5`) are unchanged - The `implementation` option and function-based `postcssOptions` API used by `@nx/webpack` are fully supported in v8 - Nx already requires Node 18+, matching postcss-loader@8's engine requirement ## Related Issue(s) Fixes #35025
18 days ago by Robert Sid...
Failed
master
63a8f27e fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE (#35028) ## Current Behavior `@nx/webpack` depends on `postcss-loader@^6.1.1`, which pulls in `cosmiconfig@7` → `yaml@1.x`. The `yaml@1.x` package has a known stack overflow vulnerability ([GHSA-48c2-rrv3-qjmp](https://github.com/advisories/GHSA-48c2-rrv3-qjmp)). ## Expected Behavior By bumping `postcss-loader` to `^8.2.1`, the transitive dependency chain is eliminated entirely — `postcss-loader@8` uses `cosmiconfig@9`, which no longer depends on `yaml` at all. This is a cleaner fix than applying a `pnpm.overrides` workaround. The upgrade is safe because: - `postcss-loader@8` peer deps (`postcss ^7||^8`, `webpack ^5`) are unchanged - The `implementation` option and function-based `postcssOptions` API used by `@nx/webpack` are fully supported in v8 - Nx already requires Node 18+, matching postcss-loader@8's engine requirement ## Related Issue(s) Fixes #35025
18 days ago by Robert Sid...
Succeeded
22.7.0-beta.8
63a8f27e fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE (#35028) ## Current Behavior `@nx/webpack` depends on `postcss-loader@^6.1.1`, which pulls in `cosmiconfig@7` → `yaml@1.x`. The `yaml@1.x` package has a known stack overflow vulnerability ([GHSA-48c2-rrv3-qjmp](https://github.com/advisories/GHSA-48c2-rrv3-qjmp)). ## Expected Behavior By bumping `postcss-loader` to `^8.2.1`, the transitive dependency chain is eliminated entirely — `postcss-loader@8` uses `cosmiconfig@9`, which no longer depends on `yaml` at all. This is a cleaner fix than applying a `pnpm.overrides` workaround. The upgrade is safe because: - `postcss-loader@8` peer deps (`postcss ^7||^8`, `webpack ^5`) are unchanged - The `implementation` option and function-based `postcssOptions` API used by `@nx/webpack` are fully supported in v8 - Nx already requires Node 18+, matching postcss-loader@8's engine requirement ## Related Issue(s) Fixes #35025
18 days ago by Robert Sid...
Succeeded
master
63a8f27e fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE (#35028) ## Current Behavior `@nx/webpack` depends on `postcss-loader@^6.1.1`, which pulls in `cosmiconfig@7` → `yaml@1.x`. The `yaml@1.x` package has a known stack overflow vulnerability ([GHSA-48c2-rrv3-qjmp](https://github.com/advisories/GHSA-48c2-rrv3-qjmp)). ## Expected Behavior By bumping `postcss-loader` to `^8.2.1`, the transitive dependency chain is eliminated entirely — `postcss-loader@8` uses `cosmiconfig@9`, which no longer depends on `yaml` at all. This is a cleaner fix than applying a `pnpm.overrides` workaround. The upgrade is safe because: - `postcss-loader@8` peer deps (`postcss ^7||^8`, `webpack ^5`) are unchanged - The `implementation` option and function-based `postcssOptions` API used by `@nx/webpack` are fully supported in v8 - Nx already requires Node 18+, matching postcss-loader@8's engine requirement ## Related Issue(s) Fixes #35025
18 days ago by Robert Sid...
Succeeded
35028
2805cb6d fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE postcss-loader 8 uses cosmiconfig@9 which no longer depends on yaml@1.x, removing the vulnerable transitive dependency path entirely.
21 days ago by Robert Sid...
Failed
35028
2805cb6d fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE postcss-loader 8 uses cosmiconfig@9 which no longer depends on yaml@1.x, removing the vulnerable transitive dependency path entirely.
21 days ago by Robert Sid...
Failed
35028
Flaky task→
2805cb6d fix(webpack): bump postcss-loader to ^8.2.1 to eliminate transitive yaml@1.x CVE postcss-loader 8 uses cosmiconfig@9 which no longer depends on yaml@1.x, removing the vulnerable transitive dependency path entirely.
22 days ago by Robert Sid...
Succeeded
master
c6990488 fix(vite): add support for Vite 8 (#34850) ## Current Behavior The `@nx/vite` plugin only supports Vite 5, 6, and 7. Users on Vite 8 get peer dependency errors: ``` peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from @nx/vite ``` ## Expected Behavior Full Vite 8 support for new and existing workspaces: **Nx plugin support:** - Update peer deps to include `^8.0.0` in `@nx/vite` and `@nx/vitest` - Default new workspaces to Vite 8 (`viteVersion = '^8.0.0'`) - Bump `@vitejs/plugin-react` to `^6.0.0` (required for Vite 8, uses Oxc instead of Babel) - Add `useViteV7` backward compatibility flag (follows existing `useViteV5`/`useViteV6` pattern) **Rolldown migration (Vite 8 replaced Rollup with Rolldown):** - Handle both `rollupOptions` (Vite <8) and `rolldownOptions` (Vite >=8) in build executor and plugin detection - Fix build executor environments API to preserve env-specific `rolldownOptions` config - Update e2e tests for Rolldown's different module counts **Type fixes for Vite 8's ESM-only declarations:** - Vite 8 ships `.d.mts` type declarations not resolvable under `moduleResolution: "node"` - Fix `typeof import('vite')` and `import type` usages across `@nx/vite`, `@nx/vitest`, `@nx/cypress`, `@nx/react`, `@nx/angular`, `@nx/remix` with inline casts - All fixes have `TODO(jack)` comments to remove when switching to `moduleResolution: "nodenext"` **Plugin compatibility:** - `@vitejs/plugin-react@^6.0.0` only supports Vite 8; `^4.2.0` for Vite <=7 - `ensure-dependencies` detects installed vite version and picks the correct plugin-react version - Cypress CT does not support Vite 8 yet — e2e test downgrades to Vite 7 **Angular vitest fix:** - `@angular/build` depends on `rolldown` which injects `@oxc-project/runtime` helpers at transform time without declaring it as a dependency - Add `@oxc-project/runtime` as an explicit devDependency in the Angular vitest generator **Docs:** - Updated supported versions table to include `^8.0.0` - Added `rolldownOptions.input` to buildable project detection docs **E2E coverage:** - New Vite 8 + React build/test e2e test - New Vite 7 + React backward compat e2e test (downgrades vite + plugin-react) - Updated environments API test for Vite 8 `rolldownOptions` - Updated incremental build test for Rolldown's module counts - Cypress CT e2e downgrades to Vite 7 (Cypress doesn't support Vite 8 yet) ## Other notes We'll do a follow-up PR to include migrations for 22.7.0. This PR's scope is only to ensure peer deps and our generators work for workspaces that are already using Vite 8. ## Related Issue(s) Fixes #34849 Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
24 days ago by Robert Sid...
Succeeded
master
c6990488 fix(vite): add support for Vite 8 (#34850) ## Current Behavior The `@nx/vite` plugin only supports Vite 5, 6, and 7. Users on Vite 8 get peer dependency errors: ``` peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from @nx/vite ``` ## Expected Behavior Full Vite 8 support for new and existing workspaces: **Nx plugin support:** - Update peer deps to include `^8.0.0` in `@nx/vite` and `@nx/vitest` - Default new workspaces to Vite 8 (`viteVersion = '^8.0.0'`) - Bump `@vitejs/plugin-react` to `^6.0.0` (required for Vite 8, uses Oxc instead of Babel) - Add `useViteV7` backward compatibility flag (follows existing `useViteV5`/`useViteV6` pattern) **Rolldown migration (Vite 8 replaced Rollup with Rolldown):** - Handle both `rollupOptions` (Vite <8) and `rolldownOptions` (Vite >=8) in build executor and plugin detection - Fix build executor environments API to preserve env-specific `rolldownOptions` config - Update e2e tests for Rolldown's different module counts **Type fixes for Vite 8's ESM-only declarations:** - Vite 8 ships `.d.mts` type declarations not resolvable under `moduleResolution: "node"` - Fix `typeof import('vite')` and `import type` usages across `@nx/vite`, `@nx/vitest`, `@nx/cypress`, `@nx/react`, `@nx/angular`, `@nx/remix` with inline casts - All fixes have `TODO(jack)` comments to remove when switching to `moduleResolution: "nodenext"` **Plugin compatibility:** - `@vitejs/plugin-react@^6.0.0` only supports Vite 8; `^4.2.0` for Vite <=7 - `ensure-dependencies` detects installed vite version and picks the correct plugin-react version - Cypress CT does not support Vite 8 yet — e2e test downgrades to Vite 7 **Angular vitest fix:** - `@angular/build` depends on `rolldown` which injects `@oxc-project/runtime` helpers at transform time without declaring it as a dependency - Add `@oxc-project/runtime` as an explicit devDependency in the Angular vitest generator **Docs:** - Updated supported versions table to include `^8.0.0` - Added `rolldownOptions.input` to buildable project detection docs **E2E coverage:** - New Vite 8 + React build/test e2e test - New Vite 7 + React backward compat e2e test (downgrades vite + plugin-react) - Updated environments API test for Vite 8 `rolldownOptions` - Updated incremental build test for Rolldown's module counts - Cypress CT e2e downgrades to Vite 7 (Cypress doesn't support Vite 8 yet) ## Other notes We'll do a follow-up PR to include migrations for 22.7.0. This PR's scope is only to ensure peer deps and our generators work for workspaces that are already using Vite 8. ## Related Issue(s) Fixes #34849 Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
24 days ago by Robert Sid...
Succeeded
master
c6990488 fix(vite): add support for Vite 8 (#34850) ## Current Behavior The `@nx/vite` plugin only supports Vite 5, 6, and 7. Users on Vite 8 get peer dependency errors: ``` peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from @nx/vite ``` ## Expected Behavior Full Vite 8 support for new and existing workspaces: **Nx plugin support:** - Update peer deps to include `^8.0.0` in `@nx/vite` and `@nx/vitest` - Default new workspaces to Vite 8 (`viteVersion = '^8.0.0'`) - Bump `@vitejs/plugin-react` to `^6.0.0` (required for Vite 8, uses Oxc instead of Babel) - Add `useViteV7` backward compatibility flag (follows existing `useViteV5`/`useViteV6` pattern) **Rolldown migration (Vite 8 replaced Rollup with Rolldown):** - Handle both `rollupOptions` (Vite <8) and `rolldownOptions` (Vite >=8) in build executor and plugin detection - Fix build executor environments API to preserve env-specific `rolldownOptions` config - Update e2e tests for Rolldown's different module counts **Type fixes for Vite 8's ESM-only declarations:** - Vite 8 ships `.d.mts` type declarations not resolvable under `moduleResolution: "node"` - Fix `typeof import('vite')` and `import type` usages across `@nx/vite`, `@nx/vitest`, `@nx/cypress`, `@nx/react`, `@nx/angular`, `@nx/remix` with inline casts - All fixes have `TODO(jack)` comments to remove when switching to `moduleResolution: "nodenext"` **Plugin compatibility:** - `@vitejs/plugin-react@^6.0.0` only supports Vite 8; `^4.2.0` for Vite <=7 - `ensure-dependencies` detects installed vite version and picks the correct plugin-react version - Cypress CT does not support Vite 8 yet — e2e test downgrades to Vite 7 **Angular vitest fix:** - `@angular/build` depends on `rolldown` which injects `@oxc-project/runtime` helpers at transform time without declaring it as a dependency - Add `@oxc-project/runtime` as an explicit devDependency in the Angular vitest generator **Docs:** - Updated supported versions table to include `^8.0.0` - Added `rolldownOptions.input` to buildable project detection docs **E2E coverage:** - New Vite 8 + React build/test e2e test - New Vite 7 + React backward compat e2e test (downgrades vite + plugin-react) - Updated environments API test for Vite 8 `rolldownOptions` - Updated incremental build test for Rolldown's module counts - Cypress CT e2e downgrades to Vite 7 (Cypress doesn't support Vite 8 yet) ## Other notes We'll do a follow-up PR to include migrations for 22.7.0. This PR's scope is only to ensure peer deps and our generators work for workspaces that are already using Vite 8. ## Related Issue(s) Fixes #34849 Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
24 days ago by Robert Sid...
Succeeded
master
c6990488 fix(vite): add support for Vite 8 (#34850) ## Current Behavior The `@nx/vite` plugin only supports Vite 5, 6, and 7. Users on Vite 8 get peer dependency errors: ``` peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from @nx/vite ``` ## Expected Behavior Full Vite 8 support for new and existing workspaces: **Nx plugin support:** - Update peer deps to include `^8.0.0` in `@nx/vite` and `@nx/vitest` - Default new workspaces to Vite 8 (`viteVersion = '^8.0.0'`) - Bump `@vitejs/plugin-react` to `^6.0.0` (required for Vite 8, uses Oxc instead of Babel) - Add `useViteV7` backward compatibility flag (follows existing `useViteV5`/`useViteV6` pattern) **Rolldown migration (Vite 8 replaced Rollup with Rolldown):** - Handle both `rollupOptions` (Vite <8) and `rolldownOptions` (Vite >=8) in build executor and plugin detection - Fix build executor environments API to preserve env-specific `rolldownOptions` config - Update e2e tests for Rolldown's different module counts **Type fixes for Vite 8's ESM-only declarations:** - Vite 8 ships `.d.mts` type declarations not resolvable under `moduleResolution: "node"` - Fix `typeof import('vite')` and `import type` usages across `@nx/vite`, `@nx/vitest`, `@nx/cypress`, `@nx/react`, `@nx/angular`, `@nx/remix` with inline casts - All fixes have `TODO(jack)` comments to remove when switching to `moduleResolution: "nodenext"` **Plugin compatibility:** - `@vitejs/plugin-react@^6.0.0` only supports Vite 8; `^4.2.0` for Vite <=7 - `ensure-dependencies` detects installed vite version and picks the correct plugin-react version - Cypress CT does not support Vite 8 yet — e2e test downgrades to Vite 7 **Angular vitest fix:** - `@angular/build` depends on `rolldown` which injects `@oxc-project/runtime` helpers at transform time without declaring it as a dependency - Add `@oxc-project/runtime` as an explicit devDependency in the Angular vitest generator **Docs:** - Updated supported versions table to include `^8.0.0` - Added `rolldownOptions.input` to buildable project detection docs **E2E coverage:** - New Vite 8 + React build/test e2e test - New Vite 7 + React backward compat e2e test (downgrades vite + plugin-react) - Updated environments API test for Vite 8 `rolldownOptions` - Updated incremental build test for Rolldown's module counts - Cypress CT e2e downgrades to Vite 7 (Cypress doesn't support Vite 8 yet) ## Other notes We'll do a follow-up PR to include migrations for 22.7.0. This PR's scope is only to ensure peer deps and our generators work for workspaces that are already using Vite 8. ## Related Issue(s) Fixes #34849 Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
24 days ago by Robert Sid...
Succeeded
master
c6990488 fix(vite): add support for Vite 8 (#34850) ## Current Behavior The `@nx/vite` plugin only supports Vite 5, 6, and 7. Users on Vite 8 get peer dependency errors: ``` peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from @nx/vite ``` ## Expected Behavior Full Vite 8 support for new and existing workspaces: **Nx plugin support:** - Update peer deps to include `^8.0.0` in `@nx/vite` and `@nx/vitest` - Default new workspaces to Vite 8 (`viteVersion = '^8.0.0'`) - Bump `@vitejs/plugin-react` to `^6.0.0` (required for Vite 8, uses Oxc instead of Babel) - Add `useViteV7` backward compatibility flag (follows existing `useViteV5`/`useViteV6` pattern) **Rolldown migration (Vite 8 replaced Rollup with Rolldown):** - Handle both `rollupOptions` (Vite <8) and `rolldownOptions` (Vite >=8) in build executor and plugin detection - Fix build executor environments API to preserve env-specific `rolldownOptions` config - Update e2e tests for Rolldown's different module counts **Type fixes for Vite 8's ESM-only declarations:** - Vite 8 ships `.d.mts` type declarations not resolvable under `moduleResolution: "node"` - Fix `typeof import('vite')` and `import type` usages across `@nx/vite`, `@nx/vitest`, `@nx/cypress`, `@nx/react`, `@nx/angular`, `@nx/remix` with inline casts - All fixes have `TODO(jack)` comments to remove when switching to `moduleResolution: "nodenext"` **Plugin compatibility:** - `@vitejs/plugin-react@^6.0.0` only supports Vite 8; `^4.2.0` for Vite <=7 - `ensure-dependencies` detects installed vite version and picks the correct plugin-react version - Cypress CT does not support Vite 8 yet — e2e test downgrades to Vite 7 **Angular vitest fix:** - `@angular/build` depends on `rolldown` which injects `@oxc-project/runtime` helpers at transform time without declaring it as a dependency - Add `@oxc-project/runtime` as an explicit devDependency in the Angular vitest generator **Docs:** - Updated supported versions table to include `^8.0.0` - Added `rolldownOptions.input` to buildable project detection docs **E2E coverage:** - New Vite 8 + React build/test e2e test - New Vite 7 + React backward compat e2e test (downgrades vite + plugin-react) - Updated environments API test for Vite 8 `rolldownOptions` - Updated incremental build test for Rolldown's module counts - Cypress CT e2e downgrades to Vite 7 (Cypress doesn't support Vite 8 yet) ## Other notes We'll do a follow-up PR to include migrations for 22.7.0. This PR's scope is only to ensure peer deps and our generators work for workspaces that are already using Vite 8. ## Related Issue(s) Fixes #34849 Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
24 days ago by Robert Sid...
Succeeded
master
c6990488 fix(vite): add support for Vite 8 (#34850) ## Current Behavior The `@nx/vite` plugin only supports Vite 5, 6, and 7. Users on Vite 8 get peer dependency errors: ``` peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from @nx/vite ``` ## Expected Behavior Full Vite 8 support for new and existing workspaces: **Nx plugin support:** - Update peer deps to include `^8.0.0` in `@nx/vite` and `@nx/vitest` - Default new workspaces to Vite 8 (`viteVersion = '^8.0.0'`) - Bump `@vitejs/plugin-react` to `^6.0.0` (required for Vite 8, uses Oxc instead of Babel) - Add `useViteV7` backward compatibility flag (follows existing `useViteV5`/`useViteV6` pattern) **Rolldown migration (Vite 8 replaced Rollup with Rolldown):** - Handle both `rollupOptions` (Vite <8) and `rolldownOptions` (Vite >=8) in build executor and plugin detection - Fix build executor environments API to preserve env-specific `rolldownOptions` config - Update e2e tests for Rolldown's different module counts **Type fixes for Vite 8's ESM-only declarations:** - Vite 8 ships `.d.mts` type declarations not resolvable under `moduleResolution: "node"` - Fix `typeof import('vite')` and `import type` usages across `@nx/vite`, `@nx/vitest`, `@nx/cypress`, `@nx/react`, `@nx/angular`, `@nx/remix` with inline casts - All fixes have `TODO(jack)` comments to remove when switching to `moduleResolution: "nodenext"` **Plugin compatibility:** - `@vitejs/plugin-react@^6.0.0` only supports Vite 8; `^4.2.0` for Vite <=7 - `ensure-dependencies` detects installed vite version and picks the correct plugin-react version - Cypress CT does not support Vite 8 yet — e2e test downgrades to Vite 7 **Angular vitest fix:** - `@angular/build` depends on `rolldown` which injects `@oxc-project/runtime` helpers at transform time without declaring it as a dependency - Add `@oxc-project/runtime` as an explicit devDependency in the Angular vitest generator **Docs:** - Updated supported versions table to include `^8.0.0` - Added `rolldownOptions.input` to buildable project detection docs **E2E coverage:** - New Vite 8 + React build/test e2e test - New Vite 7 + React backward compat e2e test (downgrades vite + plugin-react) - Updated environments API test for Vite 8 `rolldownOptions` - Updated incremental build test for Rolldown's module counts - Cypress CT e2e downgrades to Vite 7 (Cypress doesn't support Vite 8 yet) ## Other notes We'll do a follow-up PR to include migrations for 22.7.0. This PR's scope is only to ensure peer deps and our generators work for workspaces that are already using Vite 8. ## Related Issue(s) Fixes #34849 Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
24 days ago by Robert Sid...
Succeeded
master
c6990488 fix(vite): add support for Vite 8 (#34850) ## Current Behavior The `@nx/vite` plugin only supports Vite 5, 6, and 7. Users on Vite 8 get peer dependency errors: ``` peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from @nx/vite ``` ## Expected Behavior Full Vite 8 support for new and existing workspaces: **Nx plugin support:** - Update peer deps to include `^8.0.0` in `@nx/vite` and `@nx/vitest` - Default new workspaces to Vite 8 (`viteVersion = '^8.0.0'`) - Bump `@vitejs/plugin-react` to `^6.0.0` (required for Vite 8, uses Oxc instead of Babel) - Add `useViteV7` backward compatibility flag (follows existing `useViteV5`/`useViteV6` pattern) **Rolldown migration (Vite 8 replaced Rollup with Rolldown):** - Handle both `rollupOptions` (Vite <8) and `rolldownOptions` (Vite >=8) in build executor and plugin detection - Fix build executor environments API to preserve env-specific `rolldownOptions` config - Update e2e tests for Rolldown's different module counts **Type fixes for Vite 8's ESM-only declarations:** - Vite 8 ships `.d.mts` type declarations not resolvable under `moduleResolution: "node"` - Fix `typeof import('vite')` and `import type` usages across `@nx/vite`, `@nx/vitest`, `@nx/cypress`, `@nx/react`, `@nx/angular`, `@nx/remix` with inline casts - All fixes have `TODO(jack)` comments to remove when switching to `moduleResolution: "nodenext"` **Plugin compatibility:** - `@vitejs/plugin-react@^6.0.0` only supports Vite 8; `^4.2.0` for Vite <=7 - `ensure-dependencies` detects installed vite version and picks the correct plugin-react version - Cypress CT does not support Vite 8 yet — e2e test downgrades to Vite 7 **Angular vitest fix:** - `@angular/build` depends on `rolldown` which injects `@oxc-project/runtime` helpers at transform time without declaring it as a dependency - Add `@oxc-project/runtime` as an explicit devDependency in the Angular vitest generator **Docs:** - Updated supported versions table to include `^8.0.0` - Added `rolldownOptions.input` to buildable project detection docs **E2E coverage:** - New Vite 8 + React build/test e2e test - New Vite 7 + React backward compat e2e test (downgrades vite + plugin-react) - Updated environments API test for Vite 8 `rolldownOptions` - Updated incremental build test for Rolldown's module counts - Cypress CT e2e downgrades to Vite 7 (Cypress doesn't support Vite 8 yet) ## Other notes We'll do a follow-up PR to include migrations for 22.7.0. This PR's scope is only to ensure peer deps and our generators work for workspaces that are already using Vite 8. ## Related Issue(s) Fixes #34849 Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
24 days ago by Robert Sid...