-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
TASK: Allow node v16 for 7.3...8.1 #3566
Comments
Use nvm for managing your node versions :) |
any opinions @grebaldi or @markusguenther? i mean we dont have to use it in ci, but if it works id like to allow it so i dont have to edit package.json all the time 😂 (again Node 14 doesnt work or sth on my system - and i like 16 better xD) |
If it builds, v16 ought to be fine. I don't think it collides with anything (and I'm sure I've run it accidentally in my local environment on 7.3 without issues :D).
I'd like to recommend https://github.com/Schniz/fnm instead - it's the much faster option. |
One of the adjustments in #3075 was related to DevExpress/testcafe#7097 which is now closed so it might be we can clean up this snippet in the e2e tests? interestingly, i dindt encounter any issues when running the e2e test on 8.0 #3560 (i ran them on 8.0 and node 16) |
But the fetch polyfill introduced with #3075
can definitely be backported |
I'm not so sure there actually. Native fetch would require Node >= v16.15.0 (https://nodejs.org/en/blog/release/v16.15.0), and in v16, it is still behind a flag (v18 LTS removes that). |
solved by: #3589 |
On my mac, i simply cant get node 14 to run - and so far everything seems to work with node 16 as well.
The text was updated successfully, but these errors were encountered: