--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/9d354ddb-5adf-4f8b-82a4-39e76ca8e5d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Tuesday, 17 April 2018 22:07:35 UTC+10, Neil Lunn wrote:
It really only occurred to me today in preparation of a response to a question on Stack Overflow where I was including some JavaScript to run to demonstrate an example. Part of the code, which I was used to running under a modern node.js environment used the object spread syntax, which is supported under most major JavaScript execution environments presently.
However, it's not actually supported by the SpiderMonkey 45 release which is being used in the current builds. In fact, this dependency in the build ( noting both server and the mongo shell use the same engine ) has not actually been updated for some time: MongoDB 3.3.5 is released ( that's basically 2 years ago ).
Hi Neil,
It is likely that the JavaScript engine will be updated in future releases of MongoDB, but the goal isn't necessarily to maintain parity with the latest scripting engines in use by Node or other environments. Updating to a newer version of SpiderMonkey is a non-trivial update (see SERVER-23358 for some background on the 45.0.2 ESR update).
Use cases for the mongo
shell and mongod
JavaScript contexts are more limited than a full programming environment. For example, MongoDB's JavaScript integration does not currently support features like Streams, Promises, or the Console object. This generally suffices for basic administration and database interaction.
For more advanced or modern JavaScript usage I would recommend using the Node driver.
Therefore leaving any issues of ongoing and long term vision for JavaScript execution in a MongoDB "server", is their any plans at least for the client side?
I can't speculate on any future MongoDB plans beyond details you can find in the MongoDB JIRA issue tracker. There are alternative administration clients and IDEs if the mongo
shell doesn't suit your requirements for a JavaScript playground.
Regards,Stennie
It is likely that the JavaScript engine will be updated in future releases of MongoDB