xrpl.js drops Node.js 18 and 20: xrpl 6.0.0 and six other packages will need Node.js 22.12.0
The xrpl.js repository merged pull request #3585 on 16 November, dropping support for Node.js 18 and 20 in every package. Each will require Node.js 22.12.0 or later and therefore gets a major release: xrpl 6.0.0, @xrplf/isomorphic 2.0.0, ripple-address-codec 6.0.0, ripple-keypairs 4.0.0, ripple-binary-codec 3.0.0, @xrplf/secret-numbers 4.0.0 and @xrplf/mpt-crypto 0.2.0.
The pull request says there are no code changes. Node.js 20 reached end of life on 30 April 2026, and an earlier issue had announced that the next major would drop it. The floor is 22.12.0 because it is the first Node.js 22 release that can require() the ESM-only @noble and @scure 2.x dependencies; on 22.11.0, every package fails to load. On Node.js 20, npm installs with an EBADENGINE warning and the code still runs, while Yarn 1 and npm --engine-strict refuse to install. The already published xrpl@5.3.0 still installs on Node.js 20, because none of the new majors match its version ranges.
The change also adds a migration note for an earlier pull request, #3341: results of dropsToXrp() are now BigNumber values, and <, > and === give wrong results on them without TypeScript catching it - dropsToXrp('9000000') < dropsToXrp('10000000') is false, because the comparison is between strings. The note says to use .lt(), .gt(), .isEqualTo() or .isZero().
The release plan is to publish xrpl 5.4.0 from the main branch first, then merge the 6.0.0 branch, release the lower-level packages in dependency order and finally xrpl 6.0.0. The test plan reports 2,951 unit tests passing on Node.js 24, with CI on 22 and 24.

Why it matters
The engine floor is set by a dependency's module format, not by anything in xrpl.js itself, which is why the version is 22.12.0 rather than 22. Projects still on Node.js 20 keep working on the 5.x line, and the comparison note matters to anyone upgrading code that compares XRP amounts with operators.