-
Notifications
You must be signed in to change notification settings - Fork 260
fix: adjusted @types/node to pull from global setting through catalog setting #2733
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 8 Skipped Deployments
|
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.
Thank you!
@ayushboss looks like you forgot to check in the update to |
Thanks for the correction, added that in. It seems like I'm still failing one linting test, so I'm trying to figure out why that might be. |
@ayushboss the lint failures are unrelated to your changes, I'm working with the dev who introduced them to get it fixed. You can feel free to merge and ignore those |
Summary
Modified package.json of three internal packages to pull type for @types/node from the global setting, as defined in pnpm-workspace.yaml.
Rationale
I was running into versioning errors when attempting to initially clone and run turbo build on the target chains Ethereum contract. We noticed that the build error was coming from an issue with the version of node that was being run, and these modifications helped line it up.
How has this been tested?
Builds proceed as normal.