-
-
Notifications
You must be signed in to change notification settings - Fork 384
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
chore: remove Node.js 4, add Node.js 10 #128
chore: remove Node.js 4, add Node.js 10 #128
Conversation
webpack_version: latest | ||
job_part: test | ||
- nodejs_version: '4.3' | ||
- nodejs_version: '6' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't remove node@4
, it will be remove when we drop node@4 support, just add node@10
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure? See the last commits and the failing test suite. The dependencies require node >= 6.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- stage: Webpack canary | ||
before_script: yarn add git://github.com/webpack/webpack.git#master | ||
script: npm run travis:$JOB_PART | ||
node_js: 8 | ||
env: WEBPACK_VERSION=canary JOB_PART=test | ||
before_install: | ||
- 'if [[ `npm -v` != 5* ]]; then npm i -g npm@^5.0.0; fi' | ||
- npm i -g npm@latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npm@6 don't support node 4 left this as is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
node 4 is EOL and fails (see the failing unit tests of the last commits in the master branch).
We can not test further before this is not fixed: #129 Not sure where the config for CircleCI is and how it is currently configured but it seems it is not correctly working. |
@DanielRuf should be works now, can you rebase? |
Thanks for the update. Will do so later today. |
So basically these files are not there anymore so I close this PR. |
No description provided.