From e71ab494e2ec4eb602b80bb0c32405cd1c4583c0 Mon Sep 17 00:00:00 2001
From: Loris Leiva <loris.leiva@gmail.com>
Date: Tue, 1 Sep 2026 13:59:40 +0100
Subject: [PATCH] Replace the published engines field with devEngines in the JS
 client

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.
---
 clients/js/package.json | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/clients/js/package.json b/clients/js/package.json
index ec38f3d6..852334ed 100644
--- a/clients/js/package.json
+++ b/clients/js/package.json
@@ -64,7 +64,11 @@
     "peerDependencies": {
         "@solana/kit": "^8.0.0"
     },
-    "engines": {
-        "node": ">=24.0.0"
+    "devEngines": {
+        "runtime": {
+            "name": "node",
+            "version": ">=24.0.0",
+            "onFail": "error"
+        }
     }
 }