|
|
|
|
|
|
by 8n4vidtmkvmk
989 days ago
|
|
|
Well they're wrong and so is their language of choice. Any language that pollutes the global namespace when you import a lib did it wrong. For all of JS's faults, they nearly got this one right. Also, even in JS this is still a problem when you really do want all packages to share the same version of the lib, regardless if you're able to import multiple. Sometimes you just don't want multiple instances. Npm and yarn offer a solution for that too, by forcing a certain version resolution but that then you're on your own if it isn't compatible. |
|
|