chore: bump deps | wagmi focused [wip!]

[shanimal08]

Description

Motivation and Context

How Has This Been Tested?

What process can a PR reviewer use to test or verify this change?

Breaking Changes

• None
• Requires data directory on base node to be deleted
• Requires hard fork
• Other - Please specify

[gemini-code-assist]

Summary of Changes

Hello @shanimal08, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on modernizing the project's dependency stack by updating a wide array of packages to their latest versions. The primary goal is to leverage recent improvements, bug fixes, and new features, particularly within the Web3-related libraries like wagmi and viem, while also ensuring overall stability and compatibility across the application's components. This update prepares the codebase for future enhancements and maintains alignment with current best practices in frontend development.

Highlights

• Core Web3 Library Update: The wagmi library has been updated to version 3.2.0 from 2.14.16, alongside a significant bump for viem to ^2.43.5 from 2.x, ensuring the project uses the latest features and improvements in the Web3 ecosystem.
• General Dependency Refresh: Numerous other dependencies, including next, react, react-dom, @mui/material, @tanstack/react-query, i18next, motion, react-hook-form, react-i18next, styled-components, and zustand, have been updated to their latest compatible versions.
• Development Tooling Updates: Development dependencies such as eslint, eslint-config-next, @types/node, @types/react, @types/react-dom, typescript, and @tailwindcss/postcss have been upgraded, enhancing developer experience and code quality checks.
• Project Version Bump: The project's internal version in package.json has been incremented from 0.3.0 to 0.3.1, reflecting these dependency updates.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR updates multiple dependencies, with a focus on wagmi. My review highlights several major version bumps that could introduce breaking changes, which seems to contradict the PR description stating there are none. It's critical to review the release notes for these packages (i18next, next, react-i18next, wagmi, @types/node, eslint-config-next) and test the application thoroughly. I've also noted the change in versioning for viem from a loose range to a more specific one, which is a good practice for build stability but also requires careful testing.

[shanimal08]

closing in favour of #100 (less unnecessary changes)