Feature: Introduce a standalone package for Vitest + Angular support

[brandonroberts]

Which scope/s are relevant/related to the feature request?

Don't know / other

Information

This would be a standalone package for Vitest and Angular with minimal external dependencies. We currently have the Vitest integration installed with @analogjs/platform and a schematic/generator for the initial setup. This would add a @analogjs/vitest-angular package to the repository which consists of:

• Support for ng add as a standalone package
• A dependency on the @analogjs/vite-plugin-angular package
• A schematic for adding Vitest to a project manually without a hard dependency on Nx
• A builder for running unit tests with Vitest without a hard dependency on Nx

Other considerations

• Nx would still be supported in both scenarios, just not as a hard dependency
• Potentially migrating existing usage of @analogjs/platform:vitest to the new standalone builder

Describe any alternatives/workarounds you're currently using

No response

I would be willing to submit a PR to fix this issue

• Yes
• No

[brandonroberts]

cc: @yjaaidi @rainerhahnekamp

[rainerhahnekamp]

Yes, absolutely. That is the number one question: "Do I have to install the complete Analog framework for Vitest?". Having a standalone package makes it much clearer.

[brandonroberts]

The @analogjs/vitest-angular package has been released as part of Analog 1.4.0. It's a fully standalone Angular builder with no external dependencies.

Installation instructions https://www.npmjs.com/package/@analogjs/vitest-angular

Feedback is welcomed!

[rainerhahnekamp]

Thanks Brandon, will give it a try asap

[NateRadebaugh]

Works great, thanks!

One piece of feedback: it feels kind of odd importing from @analogjs/vite-plugin-angular since that's no longer an explicit dependency. I'm wondering if it would "feel better" to import the vite plugin from @analogjs/vitest-angular

[brandonroberts]

Works great, thanks!

One piece of feedback: it feels kind of odd importing from @analogjs/vite-plugin-angular since that's no longer an explicit dependency. I'm wondering if it would "feel better" to import the vite plugin from @analogjs/vitest-angular

Interesting. It's not an explicit dependency in that you are not required to use @analogjs/vite-plugin-angular. For example, @yjaaidi has a plugin also that they could use with the Vitest builder.

The plugin and the builder are still two separate packages because the plugin can be used in other environments.

[NateRadebaugh]

The plugin and the builder are still two separate packages because the plugin can be used in other environments.

Thanks yes I understand that. What I meant is that sometimes libraries will re-export its contents for a more ergonomic/abstracted API. Either way works.