No ./lib in npm release?
kainosnoema opened this issue · comments
I'm trying to install using npm v1.0.1rc9, and the lib folder isn't included at all. I've tried uninstalling and reinstalling several different ways, no luck. I don't mind manually compiling for development, but it makes deploying as a dependency almost impossible.
Strange, it builds the js before publishing. I'll have to see if I
can republish, but I'll have to ask Isaacs to reset my npm password.
On Mon, Apr 25, 2011 at 2:39 PM, kainosnoema
reply@reply.github.com
wrote:
I'm trying to install using npm v1.0.1rc9, and the lib folder isn't included at all. I've tried uninstalling and reinstalling several different ways, no luck. I don't mind manually compiling for development, but it makes deploying as a dependency almost impossible.
Reply to this email directly or view it on GitHub:
#10
Rick Olson
http://github.com/technoweenie
Must be an npm version issue. I just installed coffee-resque (transitively via another project) on a few production host VMs using the latest release version of npm (v0.8.1?). I don't remember the version of the last stable release. The package installed and I'm happy to report is purring like a kitty.
Maybe the publishing requirements and/or package structure have changed with v1.0.0.
Alright, well all the other files/folders are coming through ok and all I have to do is "make generate-js" to build the ./lib folder. Unfortunately our project requires the more automated dependency handling offered by v1.0.0. It'd be great to have the package working with the latest version as well.
+1 just wanted Rick to be aware that it may take more than a simple republish.
Evan, did v0.1.3 install correctly with your version of npm?
Yes, it did! Sorry for not letting you know... thanks!