node 16 no longer supported?

[bbannon]

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x ] My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• [x ] I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

Pull requests should be thought of as a conversation. There will be some back and forth when trying to get code merged into this or any other project. With all but the simplest changes you can and should expect that the maintainers of the project will request changes to your code. Please be aware of that and check in after you open your PR in order to get your code merged in cleanly.

Thanks!

[coliff]

If we were to drop Node 16 support there are other places it needs updating in, such as the package.json and maybe the README or docs?

[bbannon]

I didn't see it anywhere else. I may have missed it.

…

On Thu, Mar 7, 2024 at 6:34 PM Christian Oliff ***@***.***> wrote: if we were to drop Node 16 support there are other places it needs updating in, such as the package.json and maybe the README or docs? — Reply to this email directly, view it on GitHub <#3091 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHJ7GLWECJ6K6SWMZCDIK23YXEIRRAVCNFSM6AAAAABELRYZGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUHA4TCNJYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[roblarsen]

There are a couple of other places where we need to make changes

[roblarsen]

I'm going to make these changes myself.