-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kadira breaks under the new mongo driver (2.1.18, that will be soon on meteor) #234
Comments
Thanks @Fabs. |
Still experiencing this problem in v2.29.0. I've removed the package for the time being to be able to use Meteor 1.4-beta-3. |
@MechJosh0 check |
@arunoda I can confirm |
Can I use |
Having the same problem, is there a fix? |
+1 |
+1 update: v2.30.2 is working for me |
still experiencing the problem for kadira:debug |
I have the same problem here :( |
W20170320-09:30:12.360(5.5)? (STDERR) throw(ex); Any solution for this? |
I had this issue on Updating to |
Hey Guys,
I am working along with the MDG in switching the next version of meteor to the newest possible native mongodb driver. It is not fully integrated on
devel
, but will soon be on themongo-3.2
branch. You can see the PR here meteor/meteor#7104When I was testing in a project kadira broke because of the new driver.
The reason is that, even though there is still
MongoInternals.NpmModule
as a backward compatibility feature (the new place where it is expected to be since 1.0.3.2 isMongoInternals.NpmModules.mongodb.module
the new driver does not have a Connection property and thusvar originalCreateDataHandler = mongodb.Connection.createDataHandler;
throws an error.
The text was updated successfully, but these errors were encountered: