Replies: 2 comments 2 replies
-
Can you narrow this down to a minimal reproduction? Problems like this typically can't be resolved without code to look at. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks @yyx990803. I've been trying to do exactly that, and currently have the base react-ts app, with the 4 dependencies that are causing me pain, and then have introduce async imports with Frustratingly, so far I've failed to reproduce the issue. So I guess I'm wondering if there is advice on where the issue is likely to be between things like
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm attempting to migrate a large webpack React app over to vite, and have been working my way through lots of issues.
I've come up against an issue that I'm not sure how to proceed with.
I'm using
@material-ui/core
, and also@material-ui/pickers
, and also,@material-ui/lab
.I get quite a lot of warnings about `sideEffects on the dependency optimisation
89 warnings
Vite dev server running at:
ready in 17970ms.
So I suspect my issue below is related to the warnings above, but not sure how to resolve it.
When using the
@material-ui/core
library, I'm finding half of the components are present and the other half aren't. e.g.withStyles
is present, butcreateStyles
isn't. See more examples belowI assume tree shaking is in play here, but the main module doesn't seem to be getting re-hydrated in time with the components that are needed.
Any advice on how to debug this further?
Beta Was this translation helpful? Give feedback.
All reactions