-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect Vitest for in-source testing #9
Labels
Comments
That looks safe but I would rather not build in specific support for other tooling, or also make assumptions about how they need to be used. I think I would prefer to add a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Love this bundler and I appreciate the peace of mind having not to configure anything for things to just work.
Vitest does support in-source testing which I think is great when writing unit tests, however, since this bundler isn't extensible, it isn't possible for us to modify the Rollup config to tree-shake the testing code out as specified in their docs.
Would it be possible to merge the following replace config into the default Rollup config of this project? Whilst the addition of this shouldn't affect non-Vitest users, we can still include a check just incase to only include it if Vitest is present in the package.json.
The text was updated successfully, but these errors were encountered: