Frontend & browser·Modules, bundling and the build
two copies of the same library ended up in the bundle because two packages asked for different versions.
Duplicate dependency
Also calledduplicated package, multiple versions
The same package appearing more than once in the output because the version ranges could not be deduplicated. It doubles the bytes and, for anything holding module-level state, breaks it outright — two copies of a framework or a context mean instances that cannot see each other. This is why 'invalid hook call' and 'context is undefined' are so often really a resolution problem.