Package name ending in number can not be published #2658

Closed
haraldrudell opened this Issue Jul 28, 2012 · 1 comment

Comments

Projects
None yet
2 participants

Hi there,

if I try to publish a new package css3 with 'npm publish' when there is a package css, I get server response 500.

If I try to npm install css3, it installs css.

What I could see from the documentation, a trailing number is allowed?

@isaacs isaacs added a commit that referenced this issue Jul 29, 2012

@isaacs isaacs Test for #2658 9b0b53a
Owner

isaacs commented Jul 29, 2012

That's definitely weird, and I can't reproduce it. What version of npm are you using? Can you share the npm-debug.log file?

isaacs closed this Aug 15, 2012

@zkat zkat added a commit that referenced this issue Feb 2, 2016

@zkat zkat test: removed legacy-blerg3 test
this test was never actually completed. It was meant
to try to reproduce a bug ([#2658](#2658))
but didn't manage to, and was still committed.

Thanks, @isaacs! ;)
decddf7

@zkat zkat added a commit that referenced this issue Feb 2, 2016

@zkat zkat test: removed legacy-blerg3 test
this test was never actually completed. It was meant
to try to reproduce a bug ([#2658](#2658))
but didn't manage to, and was still committed.

Thanks, @isaacs! ;)
0408b54

@iarna iarna added a commit that referenced this issue Feb 2, 2016

@zkat @iarna zkat + iarna test: removed legacy-blerg3 test
this test was never actually completed. It was meant
to try to reproduce a bug ([#2658](#2658))
but didn't manage to, and was still committed.

Thanks, @isaacs! ;)
83b9eba

@iarna iarna added a commit that referenced this issue Feb 5, 2016

@zkat @iarna zkat + iarna test: removed legacy-blerg3 test
this test was never actually completed. It was meant
to try to reproduce a bug ([#2658](#2658))
but didn't manage to, and was still committed.

Thanks, @isaacs! ;)
5d5d3bf

@zkat zkat added a commit that referenced this issue Feb 12, 2016

@zkat zkat test: removed legacy-blerg3 test
this test was never actually completed. It was meant
to try to reproduce a bug ([#2658](#2658))
but didn't manage to, and was still committed.

Thanks, @isaacs! ;)
5014e66
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment