Deisling Eduard

@ygj6 Hello. Why do you think that it is react problem? I think react only calls render fn. I don't have whole picture, but here some thoughts: We can't access...

@patak-js how about this idea? We can't update this module because of imports loop, but we can prevent our page to be broken. Now every module call `performReactRefresh` during loading....

I understood that we can't write code connected to react inside Vite client... Needs more complex solution

@tzusman I can't understand the whole picture. All I know that the problem is caused by imports loop. For example you have this structure  That works during first load....

Want to have this feature too. Yarn 3 produce a huge amount of noise in logs. Im my case my log file has 9000 lines and 7800(!) of them is...

This issue makes really hard to use common Vite configs because usually common configs use npm packages. Hope the solution would be found. For now, here is my workaround: Before:...

@maketa521 I think no. One more thing - I use pnpm. Maybe this matters. Also, my node version is v16.16.0 Here is a repo for reproducing it https://github.com/edikdeisling/issue-vite-node-resolution

I use Cypress Ccomponent tests with Vite. Vite downloads huge amount of javascript modules separetly. Due to limitations of HTTP1 tests initial load is slow. Waiting for 1.5s at each...

@IanVS hello! I faced this issue too. Here is the reproduction repo https://github.com/edikdeisling/issue-storybook-preview-head Reproduction steps: 1. pnpm i 2. pnpm storybook:dev 3. // text is red 4. pnpm storybook:build 5....

are there any workarounds to avoid nx loading `.env` into global environments? While using `Vite` this behavior makes `.env` take into first place before `.env.test`