We recently found an issue where the vite bundler had multiple copies of VueRouter, which resulted in an error that was only exposed in deployed environments.
The current solution is to mark those as dedupe so vite will only use one copy, but this may just be fixing a symptom when the root cause is that the dependency should be defined in a different way.
In order to fix the build as quickly as possible we accepted the dedupe option, but this issue captures the desire to more fully understand what happened and whether our package.json(s) should be modified instead.
We recently found an issue where the vite bundler had multiple copies of VueRouter, which resulted in an error that was only exposed in deployed environments.
The current solution is to mark those as dedupe so vite will only use one copy, but this may just be fixing a symptom when the root cause is that the dependency should be defined in a different way.
In order to fix the build as quickly as possible we accepted the dedupe option, but this issue captures the desire to more fully understand what happened and whether our package.json(s) should be modified instead.