Nodejs 24 runtime support

[andrii-be]

Currently, serverless-offline supports Node.js runtimes up to version 22.x. With Node.js 24 now available on AWS Lambdas, it would be beneficial to add support for nodejs24.x as a valid runtime option in the provider configuration.

This would allow developers to:

• Test their serverless functions locally with the latest Node.js features
• Ensure compatibility before deploying to AWS Lambda when nodejs24.x support is added
• Take advantage of performance improvements and new language features in Node.js 24

The expected behavior would be to update the runtime in serverless.yml from nodejs22.x to nodejs24.x and have serverless-offline recognize and support this runtime without errors.

[crespowang]

The PR is ready .

[matthew2564]

@crespowang Will this be a new feature for both version 13.x and 14.x?

[crespowang]

@crespowang Will this be a new feature for both version 13.x and 14.x?

Is there a reason holding you back on 13?

[matthew2564]

@crespowang Will this be a new feature for both version 13.x and 14.x?

Is there a reason holding you back on 13?

I was under the impression that Serverless v3 was only compatible with serverless-offline v13. Is that the case? A number of people are tied to the free / non-licensed version(s) of Serverless.

Looking at the number of installs on NPM, v13 has ~50% more installs than v14 - I'd assume that is to do with the above.

A similar request was made last year to back-port the new runtime to v13 #1837 (comment)

[crespowang]

@crespowang Will this be a new feature for both version 13.x and 14.x?

Is there a reason holding you back on 13?

I was under the impression that Serverless v3 was only compatible with serverless-offline v13. Is that the case? A number of people are tied to the free / non-licensed version(s) of Serverless.

Looking at the number of installs on NPM, v13 has ~50% more installs than v14 - I'd assume that is to do with the above.

A similar request was made last year to back-port the new runtime to v13 #1837 (comment)

But Serverless v3 not supporting nodejs24.x is the problem, not serverless-offline.

[matthew2564]

@crespowang Will this be a new feature for both version 13.x and 14.x?

Is there a reason holding you back on 13?

I was under the impression that Serverless v3 was only compatible with serverless-offline v13. Is that the case? A number of people are tied to the free / non-licensed version(s) of Serverless.
Looking at the number of installs on NPM, v13 has ~50% more installs than v14 - I'd assume that is to do with the above.
A similar request was made last year to back-port the new runtime to v13 #1837 (comment)

But Serverless v3 not supporting nodejs24.x is the problem, not serverless-offline.

Serverless v3 was forked to an OSS version https://www.npmjs.com/package/osls to continue support.
A PR to enable node24 went in ~2 weeks ago.

[bbrodbeck-memtime]

@matthew2564 you can use serverless-offline 14 with that fork. You might need to add this to your package.json:

"overrides": {
    "serverless": "npm:osls"
  }

[crespowang]

@crespowang Will this be a new feature for both version 13.x and 14.x?

Is there a reason holding you back on 13?

I was under the impression that Serverless v3 was only compatible with serverless-offline v13. Is that the case? A number of people are tied to the free / non-licensed version(s) of Serverless.
Looking at the number of installs on NPM, v13 has ~50% more installs than v14 - I'd assume that is to do with the above.
A similar request was made last year to back-port the new runtime to v13 #1837 (comment)

But Serverless v3 not supporting nodejs24.x is the problem, not serverless-offline.

Serverless v3 was forked to an OSS version https://www.npmjs.com/package/osls to continue support. A PR to enable node24 went in ~2 weeks ago.

Ok if the oss version supports 24 then I don't see any issues serverelss-offline doesn't work with it. BUT we need to get the PR merged. There has been no updates since Nov 2024, not a good news.

[throrin19]

Any news about adding node 24 support ?

[sandro-pasquali]

Cannot start because the 'runtime: 24.x' value is read by serverless-offline and rejected. However if I simply change that to runtime: 22.x everything boots fine. So it seems that there is no real problem (runs fine on 24.x) outside of serverless-offline throwing if it sees 24. Maybe a quick release with just that number added so this package doesn't take down the whole serverless v4 system?

[andrii-be]

Thanks everyone. I can confirm I fixed it the same way — changing runtime: 24.x to 22.x. Everything works fine after that.

Sorry, I forgot to update the issue earlier. Thanks to @sandro-pasquali for pointing out the root cause — looks like serverless-offline just rejects 24.x, even though it runs fine otherwise.

From my side this can be closed, but up to maintainers whether a proper update is needed to support 24.x.

Thanks all 🙏

[sandro-pasquali]

I wouldn't say that this closes the issue exactly, but I hope the maintainers make the simple fix it implies.

Applications built in a 24.x environment will be deployed on AWS within a 22.x environment, which is not ok. It's "fine" for now as long as you don't use 24.x features that of course won't be supported in your deployed runtime.

The actual fix is to alter the check in serverless-offline that causes a terminal failure if the serverless.yml config file lists "24" in its runtime setting. I think a Warning makes sense, and even removing this check (but noting in the docs that you should use supported runtimes...) but right now this is stopping devs from deploying to a 24.x runtime on AWS.

[throrin19]

I saw the merge of node24 support, Do you have any idea when the release will be available on npm?

[felipenervo]

Any release date?

[throrin19]

@felipenervo This is why we migrate our project to serverless-localstack : it change many things but we don't have any problems and we simulate deploy and ressources directly with localstack and not with an offline wrapper (like serverless-offline-sns, ...)