3 ms·
Concerning multiple packages with the same name, is there any reason npm does not use namespaces like some other dependency/package managers do, like Composer?
by apocalyptic0n3 11y ago
Concerning multiple packages with the same name, is there any reason npm does not use namespaces like some other dependency/package managers do, like Composer? So "kik/kik" and "azer/kik" could coexist, minus legal issues of course.
- steveklabnik 11y agohttps://docs.npmjs.com/misc/scope https://docs.npmjs.com/misc/scope
- spriggan3 11y agoScopes are not mandatory when they should be.
- DrJokepu 11y agoThat would be also a pretty useful feature also for publishing your own branch of a package in npm.
- extra88 11y agoYes, this was my thought when I first heard of the controversy. I think it could make the trademark issue go away also because the potential confusion in the marketplace would be negated by the package name being paired with the author; it's not like what the package has anything to do with what Kik's services do.