-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
test: avoid vitest checking publicDir #15197
Conversation
Run & review this pull request in StackBlitz Codeflow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to disable in the vitest configs, but do we also need to disable in the manual createServer
calls? I think it might be more consistent to leave it unset.
I thought about that too. I'm slightly leaning toward not disabling it in the manual |
Because of the way we use vitest to run unit tests in the monorepo, these deep |
Perhaps we can set the |
3875bd6
There is a perf improvement now, but it will be negated if we merge: I'll remove the changes there for now then, and only leave the ones in Vitest. One problem we may have though is that if these servers start to use the public dir at one point, it may fail because we disable the feature in the vitest config for unit tests (so I still think it is better to disable them, but not a big deal) |
Description
I saw that Vitest when run in the monorepo was checking for
vite-path/public
while working on #15195. This PR disables thepublicDir
feature for vitest as we aren't using it.What is the purpose of this pull request?