Published packages fail to download eventually about npm-register HOT 21 CLOSED

does the package also exist on npm? or only in your registry?

from npm-register.

Only in my registry

from npm-register.

It doesn't use the cache for the tarballs at all, it pretty much just tries to fetch the file out of s3. Is the tarball in s3? I'm putting a log line in right now that will say Fetching... when it attempts to grab something out of s3.

from npm-register.

grab the latest HEAD version of this, that has the logging message

from npm-register.

FYI I haven't seen this happen before, and it definitely would be a major problem for us. Maybe it's s3 permissions or something?

from npm-register.

Hmm yeah it doesn't seem to be Fetching the published package. It fetches all the other ones and then looking at the log, get a 404 at

measure#request=0ms method=GET user-agent="npm/3.9.5 node/v6.2.2 win32 x64" status=404 path=/@scope/package/-/@scope/package-0.0.3/e4e40cc32eeaf250a9353243f3f6863fc7813331.tgz request_id=0.17862000812639067
measure#request=2ms method=GET user-agent="npm/3.9.5 node/v6.2.2 win32 x64" status=404 path=/@scope/package/-/@scope/package-0.0.3/e4e40cc32eeaf250a9353243f3f6863fc7813331.tgz request_id=0.01216173275852217

from npm-register.

I think this might be something related to scoped packages then. There are no conditionals on that route that I can see that would do anything other than showing that message.

from npm-register.

Come to think of it, I'm not sure I ever actually tested publishing scoped packages.

from npm-register.

It's weird, cos it works for awhile

from npm-register.

it might be client-side caching

from npm-register.

Okay I think I know what the issue is. https://github.com/dickeyxxx/npm-register/blob/master/routes/tarballs.js#L36 doesn't actually match the path that is being provided when using a @Scoped package

r.get('/:scope/:name/-/:filename/:sha', tarball)

changing to the following removes the 404 error

r.get('/:scope/:name/-/*/:filename/:sha', tarball)

But now getting a checksum error

For reference the path has the following format:
/@scope/package/-/@scope/package-0.0.4/e379749aaa127ca4933773c7801a9bc23d0e0c28.tgz

from npm-register.

try the latest HEAD, I put a patch in for this

from npm-register.

AH ok, actually can't test off HEAD on the environment we've set up since its installed via npm. Guessing haven't published recently?

from npm-register.

you can install from github, just do npm install dickeyxxx/npm-register

from npm-register.

Hmm doesn't seem to be working with PM2 after updating on the vm we're running it on

from npm-register.

Had to revert back to npm registry installed package

from npm-register.

what error are you getting? I have an idea what it might be, but without an error it's hard to know.

from npm-register.

I think the issue is running server.js didn't actually start the server

The only error I would see was in the error log was Saving files to s3 bucket <bucket>

from npm-register.

use start.js instead

from npm-register.

or better yet npm start

from npm-register.

Ok thanks, that works

from npm-register.