error when running npm install about demeteorizer HOT 6 CLOSED

See issue #17 for workaround.

from demeteorizer.

Thank you!! that worked on Modulus and Nodejitsu but not on Heroku

from demeteorizer.

Heroku may not like the sed command. You might want to check on that.

I now understand this is actually a Meteor issue, or rather a mismatch between how Meteor builds and how Demeteorizer searches for the packages used by Meteor. In Meteor 0.6.4.1 they temporarily relased it with their own fork of the mongo driver, which isn't in npm, and they called it "1.3.7-meteor" with a custom package url. Demeteorizer doesn't know how to deal with that custom package type yet. I'm hoping this will be fixed in Meteor 0.6.5 or 0.7 with them going back to the standard npm package driver. There's a few workarounds mentioned here.

Here's the options I see:

• roll back to Meteor 0.6.4, and wait for 0.6.5 or version which uses npm mongo driver again
• get sed working to replace the custom package during build. options could be
  • sed -i.bak s/1.3.7-meteor/1.3.12/ package.json
  • sed -i.bak s/1.3.7-meteor/https:\/\/github.com\/meteor\/node-mongodb-native\/tarball\/20e17040c5eccf3c431788dd281b8099cd2099f8/ package.json
• fork demeteorizer and submit pull request that handles this issue somehow

from demeteorizer.

@InconceivableDuck you understand best how Demeteorizer searches for built in packages in .meteor. Got any idea on how we could fix this perm within Demeteorizer? I don't even know if .meteor install would have the custom package URL in it for extracting... or if we just have to put in a hack for this particular issue to replace 1.3.7-meteor if found.

from demeteorizer.

The Meteor guys fixed a security whole in the MongoDB node driver. They forked the driver and created a new version called 1.3.7-meteor, which is not available in npm. I'm looking now to see if I can point the dependency to the github repo to install from there instead of npm.

from demeteorizer.

Fixed in 0.2.4 of demeteorizer.

from demeteorizer.