Skip to content

Conversation

@pxrl
Copy link
Contributor

@pxrl pxrl commented Jun 6, 2023

No description provided.

@pxrl
Copy link
Contributor Author

pxrl commented Jun 6, 2023

Also note at some point before the end of this year, we will need to get off nodejs 16.x. I tried this locally, but we have local copies of hardhat 2.9.x that anchor us to nodejs 16. So we'll need to resolve that.

Copy link
Contributor

@james-a-morris james-a-morris left a comment

Choose a reason for hiding this comment

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

In it's current state, this looks good to me

},
"engines": {
"node": ">=12"
"node": ">=16.18.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we leave TS to choose it's most recent version of node? i.e. "node": ">= 16.0.0"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will follow up on this one async 👍

@pxrl pxrl merged commit 7e7c500 into master Jun 7, 2023
@pxrl pxrl deleted the pxrl/nodejs branch June 7, 2023 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants