package.json shows "mongodb": "1.3.7-meteor"

[BretFisher]

background

I'm trying to use demeteorizer with codeship.io, which doesn't give me sudo (to install meteor) so I have to use git clone https://github.com/meteor/meteor.git ~/meteor to use meteor, which causes a few things to act differently during bundle.

First run of demeteorizer gives me this:

It's the first time you've run Meteor from a git checkout.
I will download a kit containing all of Meteor's dependencies.
Installed dependency kit v0.3.6 in dev_bundle.

=> Running Meteor from a checkout -- overrides project version (0.6.4)`

issue

I'm assuming it's the dev_bundle dependency kit which causes npm install (post bundle) to fail, which is somehow picking up the mongodb version with "1.3.7-meteor".

This is what demeteorizer puts in package.json

"mongodb": "1.3.7-meteor"

Once that's in the package.json any npm install will fail.

resolution

not sure what the core issue is: faulty meteor, faulty demeteorizer, etc.

workaround

Workaround is to use sed to remove -meteor afterward:

sed -i.bak s/-meteor// package.json

[gihrig]

@BretFisher Thanks for this. I had the same problem 'demeteorizing' a more-or-less custom app (it's from the 'Discover Meteor' book - Chapter 11).

Your solution resolved my issue.

[dancrowley303]

I am seeing this too, but only since I upgraded Meteor to 0.6.4.1. If I downgrade to 0.6.4, it works again.

[InconceivableDuck]

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.

[InconceivableDuck]

The bug has been fixed in newer versions. What I'll do it set the dependency to "1.3.x", which will just grab the latest version 1.3 version of the driver.

[InconceivableDuck]

Fixed in 0.2.4 of demeteorizer.