[poketopa]

Summary

• require Node.js 20 or later in package.json, matching the oldest runtime covered by binding CI
• update the English and Korean installation guides to state the same support floor

Rationale

PR #209 removed Node.js 18 from the test matrix and the v0.7.0 release notes record that support change. The binding matrix now verifies Node.js 20, 24, and 26 across macOS, Windows, and Linux, while the package metadata and installation guides still advertised Node.js 10-era support.

Validation

• yarn install --immutable
• just format
• just lint
• just typecheck
• just test
• git diff --check

[vercel]

@poketopa is attempting to deploy a commit to the Toss Team on Vercel.

A member of the Team first needs to authorize it.

[marshallku]

LGTM. The previous range was not accurate anyway: index.js already calls require('node:fs'), which needs Node 14.18/16+, and CI only tests Node 20/24/26. So >=20 now matches what is actually supported and tested.

Checked locally: merges cleanly into main, and the three touched files stay consistent with each other.

Severity: P1 must fix before merge · P2 should fix before merge · P3 worth fixing · P4 suggestion.

[marshallku]

P4 · release — This narrows the declared support range, so users on Node 18 will start getting an EBADENGINE warning (or an install failure with engine-strict). fix: is fine since the old range was never really supported, but it would be worth a line in the release notes, e.g. "Node.js 20 or later is now the declared minimum, matching what CI tests."