build!: drops Node 6 and 4. begin following Node.js LTS schedule #89
Conversation
|
@QmarkC thanks for the update. One thing on my mind, as we move towards the next major of each of yargs' dependencies, is if we can prefect the approach here then we should be able to ship a version of yargs that is fully functional in Node ESM, Node CJS, browser ESM, and Deno... This is completely unrelated to dropping old Node.js versions, except that I'd like to hold off on us taking the next breaking change for these libraries until we've dialed in the approach I'm describing. |
.travis.yml
Outdated
| @@ -1,7 +1,9 @@ | |||
| language: node_js | |||
| sudo: false | |||
| node_js: | |||
| - "4" | |||
| - "6" | |||
| - "10" | |||
There was a problem hiding this comment.
as we dust off these old libraries, let's switch to GitHub actions, and add automated publication/releasing, see:
https://github.com/yargs/yargs-parser/tree/master/.github/workflows
I can update the release-please.yml with the publication logic, if you add ci.yml for testing.
package.json
Outdated
| }, | ||
| "repository": { | ||
| "type": "git", | ||
| "url": "git@github.com:yargs/y18n.git" | ||
| }, | ||
| "license": "ISC", | ||
| "author": "Ben Coe <ben@npmjs.com>", |
There was a problem hiding this comment.
nit, but we should probably switch my email to bencoe@gmail.com.
|
@QmarkC I don't believe releases are setup on this repo yet, I'll do so and then merge this. |
This skips the EOL Node 8, and moves us to Node 10 as the supported Node.js version for y18n.