## Implementation Plan for Vitest E2E Support ### Changes Required: - [x] Update plugin generator schema to support "vitest" as an e2eTestRunner option - [x] Update e2e-project generator schema to add testRunner option - [x] Update e2e-project generator implementation - [x] Add new function `addVitest()` similar to `addJest()` - [x] Update `e2eProjectGeneratorInternal` to conditionally call addJest or addVitest - [x] Handle both .ts and .mts vitest config extensions - [x] Address all code review feedback - [x] Use ensurePackage for dynamic vitest import - [x] Fix syntax errors - [x] Update test template files - [x] Update plugin generator to pass testRunner to e2e-project generator - [x] Add tests for new functionality - [x] Add unit tests - [x] Add e2e test for vitest-backed plugin - [x] Update documentation - [x] Code review and refinement - [x] Address all review feedback - [x] Fix CI/Build failures (add @nx/vitest as optional peer dependency) ## Changes - **Schema updates**: Added `"vitest"` to `e2eTestRunner` enum in `@nx/plugin:plugin` generator; added `testRunner` option to `@nx/plugin:e2e-project` generator - **Implementation**: Added `addVitest()` function that configures Vitest with globalSetup/globalTeardown for local registry management, uses fork pool with singleFork for proper isolation - **Config handling**: Detects `.mts` or `.ts` vitest config files, extracts existing indentation for consistent formatting when injecting global setup/teardown - **Dependencies**: Uses `ensurePackage` to dynamically import `@nx/vitest` only when needed; added as optional peer dependency - **Testing**: Added e2e test to verify vitest-backed plugins work correctly ## Usage ```bash # Generate plugin with Vitest e2e tests nx g @nx/plugin:plugin my-plugin --e2eTestRunner=vitest # Or generate e2e project separately nx g @nx/plugin:e2e-project --pluginName my-plugin --testRunner vitest ``` Jest remains the default when no testRunner is specified.

Original prompt

> > ---- > > *This section details on the original issue you should resolve* > > vitest support for @nrwl/nx-plugin:e2e > > > > - [ ] I'd be willing to implement this feature ([contributing guide](https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md)) > > > ## Description > > I'd like to use Vitest instead of Jest for e2e testing of plugins. > > ## Motivation > > I use Vitest for everything else and it makes sense to use it for that as well. > > ## Suggested Implementation > > Add option for `nx g @nrwl/nx-plugin:plugin` to use Vitest > > ## Alternate Implementations > > I'm going to skip e2e tests altogether for now as I'm having trouble with Jest and my custom ESM setup. > > This shouldn't be terribly difficult, you'll need to add a schema option for the e2e test runner to be possible to set it to vitest and scaffold a vitest project instead of a jest project. You'll likely need a separate set of templates for the generated e2e setup, since the current ones are jest tests > > ## Comments on the Issue (you are @copilot in this section) > > > @FrozenPandaz > Would someone like to open a PR for this? > @AgentEnder > Reiterating what @FrozenPandaz said, nothing is technically blocking this feature. It should be as easy as adding a schema option and passing it through to the js generator, but we don't quite have the bandwidth to do this on the core team right now. > > It would be a great first issue for a community member. > >

- Fixes nrwl/nx#16116 --- ✨ Let Copilot coding agent [set things up for you](https://github.com/nrwl/nx/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo.