You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: