Skip to content
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

Most recently published version on npm does not match master #42

Open
dcadez opened this issue Nov 14, 2017 · 0 comments
Open

Most recently published version on npm does not match master #42

dcadez opened this issue Nov 14, 2017 · 0 comments

Comments

@dcadez
Copy link

dcadez commented Nov 14, 2017

Hello,

I have a project that uses an older version of this package to load test data into a replica set and I'm trying to update the project's node mongo driver version from 1.4.x to 2.2.x. When I tried updating this package to version 0.14.0 for compatibility with the newer mongo diver, all of my tests failed with mongo ns not found errors.

I tried pulling the package to try to figure out what the issue was only to find that when I symlinked the current code on master into my npm modules, the tests started working again. It appears that a commit that was merged in about 4 months ago has a fix for this issue by changing a collection.drop call to collection.deleteMany in the clearCollections function. However, when looking through the tags it appears that this fix was never published to npm, as the most recent publish happened a year ago.

Could a new version of this package be published with the current code on master to fix this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant