I have a package that works fine locally, but when I try to publish, I get the following Error:
Error: ENOENT, stat '/Users/scotty/Develop/Meteor/Packages/rainhaven:s3/.npm/package/npm-shrinkwrap.json' at Object.Future.wait (/Users/scotty/.meteor/packages/meteor-tool/.1.0.41.k8ayjs++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:326:15) at Object.wrapper [as stat] (/Users/scotty/.meteor/packages/meteor-tool/.1.0.41.k8ayjs++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/files.js:1124:24) at Object.files.copyFile (/Users/scotty/.meteor/packages/meteor-tool/.1.0.41.k8ayjs++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/files.js:473:21) at /Users/scotty/.meteor/packages/meteor-tool/.1.0.41.k8ayjs++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/package-client.js:269:11 ...
A google search reveals that it’s generally an issue with node unable to find a file or directory. In this case that would be:
That file definitely exists though, so I’m not really sure what’s causing the Error.
I tried deleting the npm directory and letting meteor rebuild it, but that didn’t seem to help.
Any suggestions or ideas?
Update: I just noticed that right after I run
$ meteor publish --create the meteor tools renames the package directory from my:package/.npm/package to my:package/.npm/package-new-1jtl13k when attempting to build and publish the package. As soon as it throws the error, it renames it back to package. It almost seems as though the meteor tool is looking for
rainhaven:s3/.npm/package/npm-shrinkwrap.json after that directory has been renamed.