You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloned the repo and tried npm install. I was on node 22. Got two EBADENGINE warnings; the newest supported version reported was 18. So I deleted package-lock and node_modules, switched to node 18 (fnm), and tried npm install again - only to get many many more EBADENGINE warnings. In other words, there is no node version that is compatible (according to the packages' declarations) with all the packages in the repo.
Switched back to node 22 and installed deps again, and logically enough got the same two warnings.
It does look like the examples are working, but please fix the warnings, or at least mention them in the README. And you should declare what node version we are supposed to use (I think the right way is to use the "engines" field in package.json).
The text was updated successfully, but these errors were encountered:
Thanks for raising this and clearly outlining the issue.
We're actively looking into it; addressing the package compatibility and updating the engines field in package.json accordingly. We'll also update the README to clarify supported Node versions and resolve the EBADENGINE warnings you've encountered.
Cloned the repo and tried npm install. I was on node 22. Got two EBADENGINE warnings; the newest supported version reported was 18. So I deleted package-lock and node_modules, switched to node 18 (fnm), and tried npm install again - only to get many many more EBADENGINE warnings. In other words, there is no node version that is compatible (according to the packages' declarations) with all the packages in the repo.
Switched back to node 22 and installed deps again, and logically enough got the same two warnings.
It does look like the examples are working, but please fix the warnings, or at least mention them in the README. And you should declare what node version we are supposed to use (I think the right way is to use the "engines" field in package.json).
The text was updated successfully, but these errors were encountered: