You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's well known that, at least for now, nx plugins needs to be CommonJS only, but those plugins can rely on other publishable packages from the same workspace.
Those publishable libraries, needs to be CommonJS too, but for library generators we have the option to use Vite as bundler and Vitest as unit test runner...
Considering this, would be great to have an option to use Vitest as test runner for plugins, in that way we can remove jest dependencies...
Expected Behavior
Provide also Vitest as test runner in plugin generator
This issue has been automatically marked as stale because it hasn't had any activity for 6 months.
Many things may have changed within this time. The issue may have already been fixed or it may not be relevant anymore.
If at this point, this is still an issue, please respond with updated information.
It will be closed in 21 days if no further activity occurs.
Thanks for being a part of the Nx community! 🙏
Current Behavior
Hi folks...
It's well known that, at least for now, nx plugins needs to be CommonJS only, but those plugins can rely on other publishable packages from the same workspace.
Those publishable libraries, needs to be CommonJS too, but for library generators we have the option to use Vite as bundler and Vitest as unit test runner...
Considering this, would be great to have an option to use Vitest as test runner for plugins, in that way we can remove jest dependencies...
Expected Behavior
Provide also Vitest as test runner in plugin generator
GitHub Repo
No response
Steps to Reproduce
N/A
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
I created also a discussion for this #22834
The text was updated successfully, but these errors were encountered: