npm publish missing index.js

[pgilad]

Happened to me twice already, while publishing a package I wrote (https://github.com/pgilad/gulp-angular-htmlify if it matters), the package was published without index.js.

I had no notice or info that anything went wrong during npm publish phase. But then got notified by a user that the package wasn't installing with index.js.

The only thing that I can think of that caused this, other than a bug, is that I had the project open in Vim, that may have caused a failure to publish the file.

Did anyone run into a similar case? Is there anyway to verify the package contents other than installing it as a dependency and seeing what's installed?

This happened with:
git version 1.8.3.2
npm version 1.4.6
node version 0.10.26
ubuntu 13.10

[isaacs]

I'm not sure what's going on there. Using npm version 1.4.7, I'm seeing it include the index.js when it creates a tarball from that git repo.

[gh:npm/servers/master]isaacs@urdva:~/dev/npm/servers v0.10.27-pre
$ npm cache add git+https://github.com/pgilad/gulp-angular-htmlify.git

[gh:npm/servers/master]isaacs@urdva:~/dev/npm/servers v0.10.27-pre
$ npm cache ls gulp-angular-htmlify
~/.npm/gulp-angular-htmlify
~/.npm/gulp-angular-htmlify/0.0.8/
~/.npm/gulp-angular-htmlify/0.0.8/package/
~/.npm/gulp-angular-htmlify/0.0.8/package.tgz
~/.npm/gulp-angular-htmlify/0.0.8/package/.editorconfig
~/.npm/gulp-angular-htmlify/0.0.8/package/.gitattributes
~/.npm/gulp-angular-htmlify/0.0.8/package/.gitignore
~/.npm/gulp-angular-htmlify/0.0.8/package/.jshintrc
~/.npm/gulp-angular-htmlify/0.0.8/package/.npmignore
~/.npm/gulp-angular-htmlify/0.0.8/package/.travis.yml
~/.npm/gulp-angular-htmlify/0.0.8/package/fixtures/
~/.npm/gulp-angular-htmlify/0.0.8/package/fixtures/angular-basic.html
~/.npm/gulp-angular-htmlify/0.0.8/package/fixtures/angular-complex.html
~/.npm/gulp-angular-htmlify/0.0.8/package/fixtures/angular-custom.html
~/.npm/gulp-angular-htmlify/0.0.8/package/fixtures/angular-templates.html
~/.npm/gulp-angular-htmlify/0.0.8/package/fixtures/noangular.html
~/.npm/gulp-angular-htmlify/0.0.8/package/index.js
~/.npm/gulp-angular-htmlify/0.0.8/package/license.md
~/.npm/gulp-angular-htmlify/0.0.8/package/package.json
~/.npm/gulp-angular-htmlify/0.0.8/package/readme.md
~/.npm/gulp-angular-htmlify/0.0.8/package/test.js

Can you provide any other details? If you do npm pack && tar ztvf gulp-angular-htmlify-0.0.8.tgz, what does it output?

[pgilad]

Hi this is something inconsistent that happened twice (on 2 version releases).
It happened on v0.0.6, and when I do:

$ npm cache add gulp-angular-htmlify@0.0.6
npm http GET https://registry.npmjs.org/gulp-angular-htmlify/0.0.6
npm http 200 https://registry.npmjs.org/gulp-angular-htmlify/0.0.6
npm http GET https://registry.npmjs.org/gulp-angular-htmlify/-/gulp-angular-htmlify-0.0.6.tgz
npm http 200 https://registry.npmjs.org/gulp-angular-htmlify/-/gulp-angular-htmlify-0.0.6.tgz

$ npm cache ls gulp-angular-htmlify
~\AppData\Roaming\npm-cache\gulp-angular-htmlify
~\AppData\Roaming\npm-cache\gulp-angular-htmlify\0.0.6\
~\AppData\Roaming\npm-cache\gulp-angular-htmlify\0.0.6\.cache.json
~\AppData\Roaming\npm-cache\gulp-angular-htmlify\0.0.6\package\
~\AppData\Roaming\npm-cache\gulp-angular-htmlify\0.0.6\package.tgz
~\AppData\Roaming\npm-cache\gulp-angular-htmlify\0.0.6\package\package.json
~\AppData\Roaming\npm-cache\gulp-angular-htmlify\0.0.6\package\readme.md

So you see it's missing index.js for some reason, and has an unusal .cache.json file. What other details can I provide?

If I run your command I see:

npm pack && tar ztvf gulp-angular-htmlify-0.0.8.tgz
gulp-angular-htmlify-0.0.8.tgz
tar: Record size = 18 blocks
-rw-rw-rw- 0/0             883 2014-04-17 11:00 package/package.json
-rw-rw-rw- 0/0            2094 2014-04-17 11:00 package/index.js
-rw-rw-rw- 0/0            2964 2014-04-17 11:00 package/readme.md

[pgilad]

Hi @isaacs this happened to me again on a different project I'm working on, perhaps this is machine related (Ubuntu 13.04 + 14)

I ran the following commands:

[master][~/repos/gulp-sitemap]$ npm publish
npm http PUT https://registry.npmjs.org/gulp-sitemap
npm http 201 https://registry.npmjs.org/gulp-sitemap
+ gulp-sitemap@0.2.0
[master][~/repos/gulp-sitemap]$ npm cache add gulp-sitemap@0.2.0
npm http GET https://registry.npmjs.org/gulp-sitemap
npm http 200 https://registry.npmjs.org/gulp-sitemap
npm http GET https://registry.npmjs.org/gulp-sitemap/-/gulp-sitemap-0.2.0.tgz
npm http 200 https://registry.npmjs.org/gulp-sitemap/-/gulp-sitemap-0.2.0.tgz
[master][~/repos/gulp-sitemap]$ npm cache ls gulp-sitemap
~/.npm/gulp-sitemap
~/.npm/gulp-sitemap/.cache.json
~/.npm/gulp-sitemap/0.2.0/
~/.npm/gulp-sitemap/0.2.0/package/
~/.npm/gulp-sitemap/0.2.0/package.tgz
~/.npm/gulp-sitemap/0.2.0/package/.npmignore
~/.npm/gulp-sitemap/0.2.0/package/license.md
~/.npm/gulp-sitemap/0.2.0/package/package.json
~/.npm/gulp-sitemap/0.2.0/package/readme.md

As you can see, for some reason it packed .npmignore and it didn't include index.js. I had to republish another version.

Any clue on this?

[hiddentao]

Seeing something similar with with my module - gulp-bench. I tried deleting my .npmignore prior to npm pack, all to no avail.

[hiddentao]

In my case the problem was this line in package.json:

files: ['index.js']

Duh. To get it working I changed it to:

main: 'index.js'

[pascalduez]

Same issue here happening on various projects. (i.e: grunt-sassdoc, gulp-sassdoc)

The problem is this issue is not consistent, sometimes it's fine, publishing the package with the right files, but sometimes it randomly exclude some. Often the index.js but I've also had the case with other files, like Readme and co.

I also switched from files: ['index.js'] to main: 'index.js', it makes no difference.

node v0.10.30
npm v1.4.23
OSX

[othiym23]

Is this issue still occurring with npm@2.0.0?

[pascalduez]

Is this issue still occurring with npm@2.0.0?

Hard to tell at that point, since it's happening kind of randomly.
I'll report back whenever it happens.

[othiym23]

OK. I'm going to close this for now, because I believe it's been addressed by one of the many fixes that we've made around race conditions. If it happens again, open a new ticket. Even better would be if you can include a link to a gist with the output of npm publish -ddd for a bad publish. Thanks for your patience and help!