feat: update wagmi

[ChefJerry]

---

PR-Codex overview

This PR focuses on updating the typescript, viem, and wagmi packages to newer versions, along with changing the type of timer variables from number to NodeJS.Timeout in various components and hooks for better type safety.

Detailed summary

• Updated typescript from 5.2.2 to ^5.5.4 in package.json.
• Updated viem from ^2.21.22 to ^2.22.23 in pnpm-workspace.yaml.
• Updated wagmi from ^2.12.17 to ^2.14.11 in pnpm-workspace.yaml.
• Changed let timer: number to let timer: NodeJS.Timeout in multiple files:
  • CollectWinningsPopup.tsx
  • AllHistoryCard/index.tsx
  • Features.tsx
  • useGetBlockCountdown.ts
  • useNextEventCountdown.ts
• Adjusted dependencies in pnpm-lock.yaml to reflect updated versions.

The following files were skipped due to too many changes: pnpm-lock.yaml

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2522e2a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
ton	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Feb 10, 2025 3:33am
web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 10, 2025 3:33am

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
aptos-web	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 3:33am
blog	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 3:33am
bridge	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 3:33am
games	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 3:33am
gamification	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 3:33am
uikit	⬜️ Ignored (Inspect)	Visit Preview		Feb 10, 2025 3:33am

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment	0	1.03 MB	vercel-release-bot

🚮 Removed packages: npm/@types/[email protected], npm/@types/[email protected]

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/[email protected], npm/@metamask/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[memoyil]

imo it is better to pin the version for typescript

[ChefJerry]

@SocketSecurity ignore [email protected]

[ChefJerry]

@SocketSecurity ignore @metamask/[email protected]

[ChefJerry]

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/@metamask/[email protected]