search

mbrevoort / node-reggie

An experimental light weight alternative to a full blown npm registry
416 stars 50 forks source link

`npm publish` fails for a new package #11

Closed bajtos closed 11 years ago

bajtos commented 11 years ago

When publishing a new package using npm publish and publishConfig, the command fails:

$ npm publish
npm http PUT http://localhost:8080/private-module
npm http 200 http://localhost:8080/private-module
npm http GET http://localhost:8080/private-module
npm http 404 http://localhost:8080/private-module
npm ERR! 404 'private-module' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it

Once the first version of the package is published via the reggie client, subsequent npm publish works correctly.

durango commented 11 years ago

Was this fixed by the recent merge for .13? Judging from the spec tests it seems so, but I could be wrong? Also, how do you guys recommend starting reggie under a daemon? Forever, naught, p2, or just plain ol' &?

bajtos commented 11 years ago

Was this fixed by the recent merge for .13? Judging from the spec tests it seems so, but I could be wrong?

Yes, it was fixed by that PR. I forgot to close the issue, thank you for pointing it out.

Also, how do you guys recommend starting reggie under a daemon? Forever, naught, p2, or just plain ol' &?

I am afraid I don't have any recommendation to offer here.