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
Drop support for Node.js<14.18.0 and 15 #42
Conversation
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.
Could we maybe make some reusable GitHub Actions workflows which we can use here?
Like eg:
That way we could extract the boilerplate stuff from each individual eslint-community
project and instead have them focus on what's specific for them individually.
If it is possible, that would be good, but since most of our projects need to start from a fork, I'm concerned that having the same workflow for every project would be annoying. |
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.
I think bumping to an already outdated Node.js version is a mistake which will just make us have to release another major real soon.
eslint-plugin-n
should also be bumping it's engine requirement rather than this module lower itself for it.
Thank you for your comment. I agree. I don't want to do a new major release any time soon. I will change it to support |
No description provided.