Skip to content

Conversation

@micgro42
Copy link
Collaborator

The lockfile is needed for npm audit to analyze the packages that will
be installed.

The major version upgrade to eslint was done to resolve a warning in the
latest Dependabot mail.

The lockfile is needed for npm audit to analyze the packages that will
be installed.

The major version upgrade to eslint was done to resolve a warning in the
latest Dependabot mail.

Removed all the outdated nodejs versions.
@micgro42 micgro42 force-pushed the upgradeDependencies-2021-06 branch from 7e62d2d to 9c3c626 Compare February 12, 2021 12:44
Copy link
Member

@lucaswerkmeister lucaswerkmeister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I don’t want to merge it myself since I added one commit. (Also, Travis hasn’t finished testing that commit yet.)

@micgro42
Copy link
Collaborator Author

micgro42 commented Feb 12, 2021

README: Mention Node.js compatibility change

I wonder: is that even a library that is intended to run on Nodejs? Isn't this usually a dependency of client-side JavaScript?

@lucaswerkmeister
Copy link
Member

README: Mention Node.js compatibility change

I wonder: is that even a library that is intended to run on Nodejs? Isn't this usually a dependency of client-side JavaScript?

Yes, but I thought it was still worth mentioning – since we apparently test the library on Node.js, it seems at least possible that others might also be using it there. But we could rephrase the release notes entry if you want.

@micgro42
Copy link
Collaborator Author

README: Mention Node.js compatibility change

I wonder: is that even a library that is intended to run on Nodejs? Isn't this usually a dependency of client-side JavaScript?

Yes, but I thought it was still worth mentioning – since we apparently test the library on Node.js, it seems at least possible that others might also be using it there. But we could rephrase the release notes entry if you want.

I was more thinking about: Should we add support/testing for the other LTS releases? 12, 14, maybe 16?

@micgro42
Copy link
Collaborator Author

I added a draft PR: #136
Let's see what Travis thinks.

@lucaswerkmeister
Copy link
Member

Travis seems to like it. I like it too :) not sure if it means we’d “officially” support those Node versions, but it seems useful to know in advance if something would break (we can’t test on Node v10 forever).

Add support for all current Node LTS versions
@micgro42
Copy link
Collaborator Author

From my point of view, this is now good to go 👍

@mariushoch mariushoch merged commit 35fe375 into master Feb 15, 2021
@mariushoch mariushoch deleted the upgradeDependencies-2021-06 branch February 15, 2021 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants