Manage Node.js Runtime¶
Available September 20, 2025
Manage Node.js runtimes through the nodeRuntime field in the app manifest.
Update Your Runtime for Security, Performance, and Stability¶
Updating your Node.js runtime version is important for several reasons:
- Security: Newer runtime versions include security patches and vulnerability fixes
- Performance: Updated runtimes often provide performance improvements and optimizations
- Feature Access: Access to newer JavaScript features and Node.js APIs
- Dependency Compatibility: Ensure compatibility with the latest versions of your app's dependencies
- Platform Support: Maintain compatibility with the platform's supported runtime versions
Deprecation Schedule¶
We deprecate Node.js runtimes based on the schedule provided by our compute provider, AWS. This ensures that apps run on secure, supported versions of Node.js.
| Runtime | Block Installation Date | Block Upgrade/Downgrade Date |
|---|---|---|
| Node.js 22 | TBD, Early 2027 | TBD, Early 2027 |
| Node.js 18 | Sep 30, 2025 | Oct 30, 2025 |
Deprecation Best Practices¶
When a runtime version is scheduled for deprecation, follow these best practices:
- Plan Ahead: Monitor deprecation announcements and plan your updates well in advance
- Test Thoroughly: Test your app with the new runtime version before deploying to production
- Update Dependencies: Ensure all your app's dependencies are compatible with the new runtime
- Gradual Migration: If possible, update your development and staging environments first
- Monitor Performance: After updating, monitor your app's performance and functionality
- Document Changes: Keep track of any code changes required for the new runtime version
This migration guide highlights the changes between Node.js 18 and Node.js 22 and recommendations for specific changes to look for in your apps.