Code Transition to NPM Package with weak Mongo Dependencies possible?


#1

I have written a package that uses meteor/mongo as dependency to handle a package internal collection.

This is the only dependency to the Meteor Ecosystem and I would like to make it more universal by transfering the code into an NPM package.

But I am not sure how to resolve the Mongo Dependency without hard-wiring my Meteor project to NPM Mongo peer deps.

So my question is, if there is a chance to make it a “weak” dependency so that in my meteor Project the default Mongo dep is used, while other non-Meteor projects have their deps loaded.