Skip to content
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

feat: vitest deps.experimentalOptimizer #170

Merged
merged 1 commit into from
Jun 4, 2023

Conversation

ArnaudBarre
Copy link
Member

@ArnaudBarre ArnaudBarre commented Jun 3, 2023

So actually this change is less safer than I though because it can break people using testing Vite HMR like @brillout.

I will merge this now and see the result in ecosystem CI tomorrow. My current idea is that this is rare and asking few framework authors to set this variable is ok.

Another more long term fix could be for vitest to add a flag in the transform call (like ssr) so that plugin can adapt more properly to this case.

Related PR in the SWC plugin. Original issue: vitejs/vite-plugin-react-swc#111

@ArnaudBarre ArnaudBarre force-pushed the vitest-experimentalOptimizer branch from 4a365d6 to f23d687 Compare June 4, 2023 20:58
@ArnaudBarre ArnaudBarre force-pushed the vitest-experimentalOptimizer branch from f23d687 to 78da7d8 Compare June 4, 2023 21:02
@ArnaudBarre ArnaudBarre merged commit b528c3b into main Jun 4, 2023
8 checks passed
@ArnaudBarre ArnaudBarre deleted the vitest-experimentalOptimizer branch June 4, 2023 21:13
@ArnaudBarre
Copy link
Member Author

@patak-dev So this is failing. Should we continue in this direction or find another way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant