You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does it make sense to use dedupe in this case? I mean I want to be 100% sure, that only one version of a big library gets bundled into the frontend bundle. I used dedupe for that purpose before.
Now I simply added the shared dependencies into all packages being used, with this catalog feature to sync the versions.
Is this a good approach for Vite bundles? Or I should be using dedupe as well?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using Vite in a pnpm workspace project.
My workspace file has this:
to make sure, that all my packages use the exact same files:
Does it make sense to use dedupe in this case? I mean I want to be 100% sure, that only one version of a big library gets bundled into the frontend bundle. I used dedupe for that purpose before.
Now I simply added the shared dependencies into all packages being used, with this catalog feature to sync the versions.
Is this a good approach for Vite bundles? Or I should be using dedupe as well?
Beta Was this translation helpful? Give feedback.
All reactions