Node.js 13

Node.js 13 was an odd-numbered, short-lived Current line rather than an LTS line. Compared with the preceding line, it moved to a newer V8 engine and made newer JavaScript language features available, including optional chaining and nullish coalescing. Its ECMAScript module implementation became usable without the former command-line enablement flag, although the module system still carried experimental status and behavior that later Node.js lines refined. This line also switched default builds to full ICU data, improving internationalization coverage for locales, formatting, and collation.

This cycle has reached end of life, so Node.js 13 no longer receives upstream security fixes, bug fixes, or compatibility maintenance. Its V8, OpenSSL, npm, and bundled dependency generations are old, increasing exposure to vulnerabilities and making modern tooling and package support less reliable. The early unflagged ECMAScript module behavior can also create migration friction: applications may depend on resolution, interoperation, or warning behavior that differs from supported Node.js releases. Native addons, build tooling, CI images, and deployment platforms may no longer test or provide binaries for this runtime.

Plan a move directly to a currently supported Node.js LTS line rather than treating Node.js 13 as an intermediate destination. Inventory runtime-dependent packages, native addons, build images, and deployment targets; update dependencies that do not support the target runtime; and rebuild native modules for it. Run the application and its test suite under the target Node.js version, with particular attention to ECMAScript module and CommonJS boundaries, package export and resolution rules, deprecated APIs, TLS and certificate handling, and any V8-sensitive behavior. Update CI, container base images, version-management configuration, and production runtime policies together so Node.js 13 is not reintroduced after the migration.