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

Ambiguous node version #1278

Open
blitzmann opened this issue Aug 5, 2022 · 2 comments
Open

Ambiguous node version #1278

blitzmann opened this issue Aug 5, 2022 · 2 comments
Assignees

Comments

@blitzmann
Copy link

blitzmann commented Aug 5, 2022

Describe the bug

  • The README specifies v14.17.5, however when attempting to npm i with that version there's an error stating one of the packages requires >=16 (or something to that effect)

  • /.node-version specifies 16.15.0 however there's an issue with installing on this version with Windows ( I get an error Unexpected token '.' involving libnpmfund).

  • v16.13.2 is the version that works for me

To Reproduce
Try the README version, then the .node-version on Windows 10. It's possible the latter one is an environmental issue localized to my system, but we had some coworkers report the same issue with the Unexpected token during npm i

Expected behavior
Consistent version requirements that work on all platforms

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows 10
  • Browser [e.g. chrome, safari] Chrome
  • Version [e.g. 22] latest >_>
@theClarkSell theClarkSell self-assigned this Aug 8, 2022
@theClarkSell
Copy link
Member

@all-contributors please add @blitzmann for bug

@allcontributors
Copy link
Contributor

@csell5

@blitzmann already contributed before to bug

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