Node.js v24 now available for Twilio Functions
Twilio Functions now supports Node.js v24 as a build runtime, selectable via the Console or Serverless Toolkit configuration. The upgrade requires @twilio/runtime-handler version 2.1.2 or later, with automatic upgrades available for compatible services during deployment.
Twilio Functions now supports Node.js v24 as a build runtime. You can target it by selecting Node.js v24 from the runtime dropdown in the Console Dependencies tab, or by specifying runtime: node24 in your Serverless Toolkit configuration.
Node.js v24 requires @twilio/runtime-handler version 2.1.2 or later. If your service specifies a version between 1.2.0 and 2.1.2, Twilio will automatically upgrade it to 2.1.2 when you deploy to node24 — no action required. If your service specifies a version below 1.2.0, your build will fail with an error asking you to upgrade manually before deploying to node24.
Functions currently deployed on earlier runtimes are unaffected. Node.js v22 remains the current default.
To upgrade your runtime or learn more about supported versions, see the Node.js version upgrade guide and the Migrating Functions from callback to async/await documentation.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Integrity now supports all three major US networks
Voice Integrity, part of Twilio's Voice Trust offering, now supports all three major US carrier networks. Businesses can register their details and outbound phone numbers directly with carriers to help identify legitimate traffic and reduce spam blocking.
Unified Login for SendGrid Marketplace Customers
SendGrid marketplace customers can now create individual Twilio logins for each user, enabling granular permission management instead of shared admin access. This rollout applies to all marketplace integrations including Azure, Google Cloud, Heroku, and AWS.
Webhook Configuration API is now Generally Available
The Webhook Configuration API enables customers to configure authentication and delivery settings for outbound webhooks on a per-URL basis through Webhook Settings and Webhook Rules resources.