-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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: add Node.js 8 and 10 #100
Conversation
Codecov Report
@@ Coverage Diff @@
## master #100 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 3 3
Lines 194 194
Branches 33 33
=====================================
Hits 194 194 Continue to review full report at Codecov.
|
@DanielRuf what's this pr for? |
This PR is to add Node.js 8 and 10 to the Travis builds so we can run the unit tests on these versions too and catch Node.js 8 and 10 bugs earlier and make sure that also these stable and LTS releases are supported. |
Yes, I know what's this config used for. I'm not sure if we need it. Actually we have all these tests in the past. You could see a Just wondering if our unit test runs perfectly on Node6, a lower node version, dose that mean it shoud be good on 8 and 10? Plus, will this expand the total CI process time? |
No, not in general. These do normally use a test matrix.
Why not? There can be always changes in Node.js which affect libraries.
You can constrain it to a specific Node.js version / test. |
Regarding different Node.js versions and testing: webpack/watchpack#80 (comment) Also older versions (4 is EOL) often break and dependencies are often not compatible anymore (eg puppeteer requires Node.js 6+). |
https://github.com/webpack/webpack-cli/blob/master/.travis.yml#L42 Travis Ci is very flexible. |
All right, may be we could give it a try |
Let's give it a try. |
🎉 This PR is included in version 1.5.20 🎉 The release is available on: Your semantic-release bot 📦🚀 |
No description provided.