Skip to content

Replace the published engines field with devEngines in the JS client - #177

Merged
lorisleiva merged 1 commit into
mainfrom
loris/drop-published-engines
Sep 1, 2026
Merged

Replace the published engines field with devEngines in the JS client#177
lorisleiva merged 1 commit into
mainfrom
loris/drop-published-engines

Conversation

@lorisleiva

Copy link
Copy Markdown
Member

This PR removes the engines field from the published JS client manifest and declares the Node 24 dev-tooling floor via devEngines.runtime instead. engines constrains consumers rather than contributors — Yarn Classic hard-fails installing the client into any project running Node < 24 — while the client's actual runtime floor is simply inherited from @solana/kit. devEngines only applies to this repository's own development and is enforced by npm ≥ 10.9. Fixes #176.

The engines field ships in the published manifest and constrains consumers rather than contributors: Yarn Classic hard-fails installing the client into any project running Node < 24, while the client's actual runtime floor is simply inherited from @solana/kit. The Node 24 requirement is a dev-tooling concern only, so it is now declared via devEngines.runtime, which applies exclusively to this repository's own development and is enforced by npm >= 10.9.
@lorisleiva
lorisleiva merged commit c56b82b into main Sep 1, 2026
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Published JS client sets engines.node >=24, breaking Yarn Classic installs on Node 22

1 participant