404 on node package install

[jglamine]

I get a 404 when trying to install the node package:

npm install --save-dev lunr

[Ehesp]

Same...

[olivernn]

Thanks for reporting this issue, could you please add more details about the error, I assume npm is spitting out some error messages, including them here would make debugging this easier for me.

[Ehesp]

No worries:

npm -v: 1.1.21

C:\Users\Me\Documents\Development\ionic>npm install lunr -g
npm http GET https://registry.npmjs.org/lunr
npm http 304 https://registry.npmjs.org/lunr
npm http GET https://registry.npmjs.org/lunr/-/lunr-0.5.0.tgz
npm http 404 https://registry.npmjs.org/lunr/-/lunr-0.5.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/lunr/-/lunr-0.5.0.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\fetch.js:57:12
npm ERR!     at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at fs.js:1596:14
npm ERR!     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:103:5
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/isaacs/npm/issues>

Pretty much whats happening for me!

[olivernn]

Thanks. Looking at that I'm not sure this is an issue with lunr, looks more like a problem with npm to me. Maybe open an issue on npm, be sure to link to this issue aswell so I can follow along.

[olivernn]

Are you still having this issue, I just tried locally and it works for me:

⚡  ~ ➭ npm install lunr -g
npm http GET https://registry.npmjs.org/lunr
npm http 304 https://registry.npmjs.org/lunr
[email protected] /usr/local/share/npm/lib/node_modules/lunr

Having said that, this is the output from http://registry.npmjs.org/lunr/-/lunr-0.5.0.tgz

{
  error: "not_found",
  reason: "Document is missing attachment"
}

Did you open an issue with npm?

[jglamine]

I haven't opened an issue with npm yet. The 304 means you're loading a
locally cached version. Does clearing your npm cache allow you to reproduce
the error?
On Mar 31, 2014 3:24 PM, "Oliver Nightingale" [email protected]
wrote:

Are you still having this issue, I just tried locally and it works for me:

⚡ ~ ➭ npm install lunr -g
npm http GET https://registry.npmjs.org/lunr
npm http 304 https://registry.npmjs.org/lunr
[email protected] /usr/local/share/npm/lib/node_modules/lunr

Having said that, this is the output from
http://registry.npmjs.org/lunr/-/lunr-0.5.0.tgz

{
error: "not_found",
reason: "Document is missing attachment"
}

Did you open an issue with npm?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/77#issuecomment-39130093
.

[olivernn]

Yeah, it was cached when it worked for me. I've tried re-publishing and un-publishing and re-publishing but still no dice.

I've opened an issue on npm, I don't think this is an issue my end, since I've not changed the way I've published to npm from any other version, we'll see.

Sorry for any inconvenience this is causing!

[Ehesp]

It's worked for me now, HTTP 200.

[jglamine]

It works now, but it's getting lunr version 0.4.5. I think the latest is
supposed to be 0.5.0. Did you accidentally remove the latest version?
On Apr 1, 2014 2:15 PM, "Elliot Hesp" [email protected] wrote:

It's worked for me now, HTTP 200.

Reply to this email directly or view it on GitHubhttps://github.com//issues/77#issuecomment-39239253
.

[olivernn]

@Ehesp check the version, it's probably 0.4.5 (though if it isn't well done!)

@jglamine the details are in the npm issue, tl;dr: I tried re-publishing the other advice was to un-publish and re-publish, still no luck.

I'll update here when I know more but you might want to follow npm/npm#4988

[Ehesp]

Oh, yeah it is :(

[olivernn]

Quick update, I've bumped the version to 0.5.1 (despite nothing changing 😡) and tried to publish again. I'm still seeing errors from npm despite it having created the version. You still won't be able to install 0.5.1.

[olivernn]

This should now be fixed, 0.5.2 is the good version.

My npm was out of date, upgrading solved the issue, though I really think npm should have handled this more gracefully.