Skip to content

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

Merged
merged 2 commits into from
May 27, 2025

Conversation

ayushboss
Copy link
Contributor

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?

  • Current tests cover my changes
  • Added new tests
  • Manually tested the code

Builds proceed as normal.

@ayushboss ayushboss requested a review from a team as a code owner May 26, 2025 19:31
Copy link

vercel bot commented May 26, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

8 Skipped Deployments
Name Status Preview Comments Updated (UTC)
api-reference ⬜️ Skipped (Inspect) May 27, 2025 4:12pm
component-library ⬜️ Skipped (Inspect) May 27, 2025 4:12pm
developer-hub ⬜️ Skipped (Inspect) May 27, 2025 4:12pm
entropy-debugger ⬜️ Skipped (Inspect) May 27, 2025 4:12pm
entropy-explorer ⬜️ Skipped (Inspect) May 27, 2025 4:12pm
insights ⬜️ Skipped (Inspect) May 27, 2025 4:12pm
proposals ⬜️ Skipped (Inspect) May 27, 2025 4:12pm
staking ⬜️ Skipped (Inspect) May 27, 2025 4:12pm

Copy link
Collaborator

@cprussin cprussin left a comment

Choose a reason for hiding this comment

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

Thank you!

@cprussin
Copy link
Collaborator

@ayushboss looks like you forgot to check in the update to pnpm-lock.yaml, please add that to resolve the CI failures

@vercel vercel bot temporarily deployed to Preview – insights May 27, 2025 16:12 Inactive
@vercel vercel bot temporarily deployed to Preview – developer-hub May 27, 2025 16:12 Inactive
@vercel vercel bot temporarily deployed to Preview – api-reference May 27, 2025 16:12 Inactive
@vercel vercel bot temporarily deployed to Preview – staking May 27, 2025 16:12 Inactive
@vercel vercel bot temporarily deployed to Preview – entropy-explorer May 27, 2025 16:12 Inactive
@vercel vercel bot temporarily deployed to Preview – entropy-debugger May 27, 2025 16:12 Inactive
@vercel vercel bot temporarily deployed to Preview – proposals May 27, 2025 16:12 Inactive
@vercel vercel bot temporarily deployed to Preview – component-library May 27, 2025 16:12 Inactive
@ayushboss
Copy link
Contributor Author

@ayushboss looks like you forgot to check in the update to pnpm-lock.yaml, please add that to resolve the CI failures

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.

@cprussin
Copy link
Collaborator

@ayushboss looks like you forgot to check in the update to pnpm-lock.yaml, please add that to resolve the CI failures

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

@ayushboss ayushboss merged commit 379cdd7 into main May 27, 2025
12 of 13 checks passed
@ayushboss ayushboss deleted the fixing-node-types-version branch May 27, 2025 17:30
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.

2 participants