Update mongodb dependency in sails-mongo

[galcivar]

Sails version:1.0.2
Node version:8.11.1
NPM version: 6.0.0
DB adapter name: sails-mongo
DB adapter version: 1.0.1
Operating system: WIndows

---

Update the sails-mongo dependency of mongodb from v2.2.25 to mongodb v2.2.35

This allows the usage of Mongo 3.6 (Adding {cursor: {}} to any aggregation call)

[sailsbot]

Hi @galcivar! It looks like you may have removed some required elements from the initial comment template, without which I can't verify that this post meets our contribution guidelines. To re-open this issue, please copy the template from here, paste it at the beginning of your initial comment, and follow the instructions in the text. Then post a new comment (e.g. "ok, fixed!") so that I know to go back and check.

Sorry to be a hassle, but following these instructions ensures that we can help you in the best way possible and keep the Sails project running smoothly.

*If you feel this message is in error, or you want to debate the merits of my existence (sniffle), please contact inquiries@sailsjs.com

[galcivar]

ok, fixed!

[sailsbot]

@galcivar Thanks for posting, we'll take a look as soon as possible.

---

For help with questions about Sails, click here. If you’re interested in hiring @sailsbot and her minions in Austin, click here.

[professor-rage]

MongoDB source:

Changed in version 3.6: MongoDB 3.6 removes the use of aggregate command without the cursor option unless the command includes the explain option. Unless you include the explain option, you must specify the cursor option.

https://docs.mongodb.com/manual/reference/command/aggregate/

MongoError: The 'cursor' option is required, except for aggregate with the explain argument

[xbassols]

That's correct. I'm having the same issue.

[AtiX]

It seems like this issue would be fixed by this open PR if I am not mistaken.

[raqem]

Hi all @galcivar @xbassols @professor-rage I dont have an update on the timeline for the pull request being merged but please check out the open PR mentioned by @AtiX for a possible work around for this issue.