3 ms·
Couldn't you version shared modules to avoid this?
by esperent 6y ago
Couldn't you version shared modules to avoid this?
- Vinnl 6y agoWhat do you mean by "versioning" them? If you mean running two different versions of the same library and putting them in different shared modules, then: maybe, that depends on the library. I'm quite sure that that's not possible with React, though, and I've experienced the same problem at a previous employer that insisted on using Polymer: Web Components have their own tag name (e.g. <google-maps>), and you can't run multiple versions of them at the same time because they'll both want to claim that tag.