-
Notifications
You must be signed in to change notification settings - Fork 66
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
Tests are failing on Node 8.3 #657
Comments
why would someone use node 8.3? LTS is 8.15.1 |
We don't know what version people are using on their machines or in their docker images. The README just says "You need Node 8 or newer.". It's a bug. The issue was introduced by a recent change ( |
given the fact, that node 8.3 is almost 2 years old, and that node 8.x will be EOL end of this year, I don't think we should try to fix this problem. Also, I understand "You need Node 8 or newer." as, you need the latest 8.x node... My suggestion is:
|
and add appropriate version checks and error messages... I'd rather remove Node 8 support and require Node 10. |
Some more details:
|
we can't really fix it without implementing the entire resolve logic ourselves. I don't think its' worth it. I think:
@trieloff, @stefan-guggisberg, @kptdobe, @rofe, @koraa WDYT? |
please comment on: #683 |
Description
helix-cli
doesn't function properly on Node version 8.3.To Reproduce
Steps to reproduce the behavior:
nvm use 8.3
npm test
Expected behavior
npm test
succeeds on node 8.3.Version:
hlx >0.13.8
The text was updated successfully, but these errors were encountered: