Is it V8? Can’t seem to find this information.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As of v3.1.7 it is SpiderMonkey – confirmed on the MongoDB 3.2 release notes.
The reasons are explained on the compatibility notes:
There are some further notes on here.
A recent MongoDB release v3.3.5 received an update to the SpiderMonkey version to 45.0.2 ESR.
Development on switching back to SpiderMonkey from V8 was carried out in the v3.1.6 release – see SERVER-18531, but SpiderMonkey was not enabled by default until v3.1.7 – see SERVER-19376.
Before v3.1.6 it was the V8 JavaScript engine, which became the default in v2.3.1, according to the release notes and is also highlighted in the v2.4 release notes.
SpiderMonkey was removed from the source in v2.5.1
Before that, it was an extended SpiderMonkey v1.7 shell that used some non-standard JavaScript extensions, for example the ECMAScript for XML extensions.
It seems to have been V8 even further back, but was migrated in April 2009 from V8 to SpiderMonkey. It looks like it was still SpiderMonkey for MongoDB in v1.1.4 according to this post, but I can’t find out when the original switch was.