guys, please do it soon. its got nearly 3 years since the initiation of the feedback.

Really need this update

wakeup guys! We are in 2024 now.

Hey all! We have several projects on functions underway and hope to have something very exciting to announce for you all in the upcoming year. To shed some more light on the feedback item here, we maintain and run our own custom JS runtime. As part of that, there is a minimum compatibility guarantee of Node v10 APIs, but we have implemented support beyond v10 for various packages. The product team would love to learn more and gather your feedback on this – take our survey! https://forms.gle/TrKfPyimNF7h6UGs5

This product (triggers) is becoming unusable. No modern packaged support node 10

I dont think that they are gonna prioritize that. The good think is that they provide AWS Eventbridge without the need to be dependent on Atlas to integrate it and it works like a charm.

Any update on this? I just received an email from Vercel that they are ending support for Node 16 in June of 2024 for their functions and encouraging users to upgrade to Node 18. I'd like to continue using Atlas Functions, but it feels so far behind with little transparency on what the plan is to address this.

We want to use the Apple's App Store Server Library (https://github.com/apple/app-store-server-library-node) to handle app subscriptions and renewals server to server. It requires node js 16+.

@laura, any updates you can provide about this project now that we're 3 months on from your initial post? Just looking for some reassurance that this significant issue will get better soon. Thanks

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.

Hi all, we're excited to be kicking off a project this quarter focused on improving Atlas Functions based on feedback we've heard from you. It's a top priority on our roadmap and we'll definitely keep you updated on details as they become available. In the meantime, we do track requests around unsupported packages so if there are specific ones you're running into issues with or would like to see, please drop a comment. Thanks!

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.

Oh no, this is now becoming a deal breaker for my company too. Since the MongoDB team doesn't seem to read this anyway: any good alternative vendors or workarounds anyone found?

I would love it if each App Services Function could individually choose which Node version to use.

Discovered that @mapbox/mapbox-sdk doesn't work... :-(

The latest major versions of both the Twilio and Stripe libraries no longer work in Atlas functions. This is critical now. In the not too distant future the previous major versions will be unsupported, which is an untenable situation to be in. To quote an earlier poster: "Dear Mongodb team, could you give [us] a short feedback if this is on your roadmap?" Otherwise, I will have to seriously reconsider how much I'm leveraging Atlas. I don't mean that in a sassy way, just literally I can't get my business in a situation where our other vendors won't support us, and Atlas is forcing that situation on me at this point. Thanks.

One major issue now is that major packages, like jsonwebtoken, no longer support Node v10. This means downgrading to unsecure, unsupported packages or just not using Functions at all.

This is has started becoming more problematic lately and cost us time trying to utilize certain libraries that aren't supported. LTS is now 18.15. I'd like to see a move to at least v16 at this point.

Dear Mongodb team, could you give as a short feedback if this is on your roadmap? The issue is that we have to use old versions of sdks which will reach their end-of-support soon. As an example, the aws-sdk is currently only usable in v2 which will be put in maintenance mode by aws this year (2023). It will then still be usable but after that they will discontinue support which means that it is not garanteed to work anymore. While this is still in the future, it would be reassuring to know that you have plans to upgrade the node version. Thanks in advance for your answer. Daniel

I love App Services, but this is the kind of thing that when you find out about it you start to question the platform. Having a node version this out of date is simply unacceptable. Beyond appearances, I ran into issues with the date-fns-tz module because of node v10's limited support for Intl.