Closed ungoldman closed 8 years ago
(as in >> Sorry, that package name is taken! :(
when it's actually free)
I think I'm going to let people create the package even if the name's taken and just have it be a warning. There's cases where it's not at all relevant if the package name is available on npm (private module, private npm).
Yeah I agree, users should be able to bypass this check.
I'm getting stopped by any name right now... I'm going to have to remove it for now.
? name: (blarg) blarg123456789
>> Sorry, that package name is taken! :(
OK. Really strange... If I send a patch with a way to easily bypass would you accept it?
Only if it's accurate in terms of reporting package name availability. I'll have to test more to figure it out
Closing this for now.
Getting a false negative for
parse-wkid
from can-haz-package.Will investigate further when I have a minute. cc @Flet