Mohammed
My feedback
4 results found
-
70 votes
An error occurred while saving the comment An error occurred while saving the comment Mohammed
commented
We need this too. The latest popular libraries don't work with this ancient node 10 version. Please upgrade to the latest LTS as soon as possible or let us choose the versions.
Mohammed
supported this idea
·
-
5 votes
An error occurred while saving the comment Mohammed
commented
We need this too. This is important to preview our changes without pushing it to users.
Or even open an API to let us add Allowed Request Origins if you can't support a wildcard.Mohammed
supported this idea
·
-
56 votesMohammed
supported this idea
·
-
2 votesMohammed
shared this idea
·
Hey Laura, good to finally hear the team is gonna work on this. Examples of packages that don't work and issues we've had with this old node version are as follows:
- Sentry doesn't work at all (@sentry/node): this is a popular logging service that we use to log errors across our stack (web/mobile/[backend]). Currently, we can't get our code logs from mongodb functions. The log forwarder feature isn't useful so don't suggest it (because the log forwarded just dumps everything, we want just the logs we specify write in our code)
- Stripe (payments), we are using a super old version to get around this
- Uploading binary files with FormData. MongoDB forms only support strings. We get errors as soon as we try to send a FormData with a field that is binary.
- Packages that use JWTs are also broken (as mentioned below). These are 3rd party packages (we know MongoDB provides JWT in the context).
- And basically, any nodejs library that has a dependency on any of the things mentioned above or language features from later versions of node.
Node 10 is very old, we need at least node 16 or better the ability to choose the node version for each function or app.