Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor: EBADENGINE (regardless what node version one uses), non-obvious which node version I should use #9

Open
dagjoh opened this issue Mar 7, 2025 · 1 comment

Comments

@dagjoh
Copy link

dagjoh commented Mar 7, 2025

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).

@Vheissu
Copy link
Member

Vheissu commented Mar 8, 2025

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.

Appreciate the heads-up!

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

No branches or pull requests

2 participants