Feature Request: Add Node 24 (Active LTS) Support
Package: @twilio/flex-plugin-scripts (and potentially other packages in this monorepo)
Repo: twilio/flex-plugin-builder
Summary
The engines field in packages/flex-plugin-scripts/package.json currently reads:
"engines": {
"node": "^16 || ^18 || ^20 || ^22"
}Node.js 24 reached Active LTS status in April 2025, meaning it is now the recommended version for production use. Many teams — including ours — are actively upgrading CI pipelines and development environments to Node 24 as part of standard dependency hygiene. The current constraint causes a hard engine warning (or failure with --engine-strict) and creates friction for any team that has already moved to Node 24.
Requested Change
Update the engines field in packages/flex-plugin-scripts/package.json to include Node 24:
"engines": {
"node": "^16 || ^18 || ^20 || ^22 || ^24"
}
Broader Ask: Audit All Packages in This Monorepo
This repo appears to contain multiple packages under packages/. It would be worth auditing the engines field across all of them for consistency, since a mismatch between packages in the same monorepo can cause confusing install or runtime failures for consumers. If the team is open to it, a single PR that bumps all affected packages at once would be a clean, low-risk improvement.
Packages likely worth checking:
@twilio/flex-dev-utils@twilio/flex-plugin@twilio/flex-plugin-test@twilio/flex-plugin-webpack@twilio/flex-plugins-api-client- Any others under
packages/
Why This Is Low Risk
Node 24 is largely backward-compatible with the Node 22 range already supported. The V8 engine upgrade and standard library changes in Node 24 are unlikely to affect the core build, test, and deploy scripts this package provides. That said, adding Node 24 to the CI matrix (e.g., a .node-version or GitHub Actions matrix entry) alongside the change would give the team confidence before publishing.
Context
Thanks for maintaining this toolchain — it's a critical part of the Flex plugin development workflow. Happy to submit a PR for this if the team would prefer a community contribution.
Feature Request: Add Node 24 (Active LTS) Support
Package:
@twilio/flex-plugin-scripts(and potentially other packages in this monorepo)Repo:
twilio/flex-plugin-builderSummary
The
enginesfield inpackages/flex-plugin-scripts/package.jsoncurrently reads:Node.js 24 reached Active LTS status in April 2025, meaning it is now the recommended version for production use. Many teams — including ours — are actively upgrading CI pipelines and development environments to Node 24 as part of standard dependency hygiene. The current constraint causes a hard engine warning (or failure with
--engine-strict) and creates friction for any team that has already moved to Node 24.Requested Change
Update the
enginesfield inpackages/flex-plugin-scripts/package.jsonto include Node 24:Broader Ask: Audit All Packages in This Monorepo
This repo appears to contain multiple packages under
packages/. It would be worth auditing theenginesfield across all of them for consistency, since a mismatch between packages in the same monorepo can cause confusing install or runtime failures for consumers. If the team is open to it, a single PR that bumps all affected packages at once would be a clean, low-risk improvement.Packages likely worth checking:
@twilio/flex-dev-utils@twilio/flex-plugin@twilio/flex-plugin-test@twilio/flex-plugin-webpack@twilio/flex-plugins-api-clientpackages/Why This Is Low Risk
Node 24 is largely backward-compatible with the Node 22 range already supported. The V8 engine upgrade and standard library changes in Node 24 are unlikely to affect the core build, test, and deploy scripts this package provides. That said, adding Node 24 to the CI matrix (e.g., a
.node-versionor GitHub Actions matrix entry) alongside the change would give the team confidence before publishing.Context
Thanks for maintaining this toolchain — it's a critical part of the Flex plugin development workflow. Happy to submit a PR for this if the team would prefer a community contribution.