Update dependencies Aug 24

[rin-st]

Description

• Updates dependencies
• Adds react-copy-to-clipboard types definition since after updates types breaks
• updated husky script and pre-commit. See "How to migrate" block https://github.com/typicode/husky/releases/tag/v9.0.1
• removed nextjs/out folder from formatting
• Adds yarn plugin that helps to update all the packages. How to use: yarn upgrade-interactive

---

There are still possible updates:

But I think we don't need to touch it for now:

• abitype breaks types since it differs from viem
• chai breaks hardhat
• eslint/prettier packages - revert #875 #905
• types/node v18 since we use node v18 for now

---

Tried all the scripts from root package.json and looks like everything works as expected

Additional Information

• I have read the contributing docs (if this is your first contribution)
• This is not a duplicate of any existing pull request

[technophile-04]

Lol I am afraid and procrastinating to test this

Probably we could have divided this in to :

1. updating Wagmi , Viem, Abitype, Rainbowkit versions
2. Next, react, react-dom all realted package versions
3. Typescript, eslint, eslint typescript etc versions
4. Hardhat updagrades
5. Maybe packages which has major bump a separate PR for each example:
   • usehooks-ts (we had some issues with it previously Up usehooks ts #707 , usehooks-ts patch is not applied on vercel deployment #706)
   • uniswap-v2-sdk
   • ...
6. then rest of remaining small packages?

Maybe sounds a lot of work but this way we make sure there are less unrecognised bugs and if we find a bug its easy to find out to which thing it belongs? because sometimes really wired bug appear like #555 (comment) and hard to debug too

but lol maybe I am being too much cautious

[technophile-04]

Ohh probably if usehooks works nicely now, we could remove use-debounce? since we have a debounce hook in usehookts.ts?

https://usehooks-ts.com/react-hook/use-debounce-value

[rin-st]

Probably we could have divided this in to :

You mean create pr for every step, test it, backmerge to create-eth, test it, create new one etc? Looks very slow, but if you want I can create different pr's it's easy.

---

As an option, you can for example test commit by commit, which is divided into logical blocks. It's not ideal, but I think it's ok. And then only bugfixes prs if needed

[rin-st]

Are you getting this warning on nextjs terminal btw?

<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Unable to snapshot resolve dependencies

Didn't notice it first. This doesn't help.

Upd. getting this warning on main too 🤷‍♂️

[rin-st]

Last react-query version 5.53.1 (3 hours ago) breaks requests with BigInts in response (for example requesting balance of the connected wallet). I need to update structuralSharing or fix serializing or probably they will change this behavior on next versions. I'll update it later

[rin-st]

Last react-query version 5.53.1 (3 hours ago) breaks requests with BigInts in response (for example requesting balance of the connected wallet). I need to update structuralSharing or fix serializing or probably they will change this behavior on next versions. I'll update it later

Throwing error was fixed in 5.53.3 so Balance will work as expected, but without ee3400f warnings still will be on the console

[rin-st]

Lol I am afraid and procrastinating to test this

Probably we could have divided this in to :

1. updating Wagmi , Viem, Abitype, Rainbowkit versions

2. Next, react, react-dom all realted package versions

3. Typescript, eslint, eslint typescript etc versions

4. Hardhat updagrades

5. Maybe packages which has major bump a separate PR for each example:

   • usehooks-ts (we had some issues with it previously Up usehooks ts #707 , usehooks-ts patch is not applied on vercel deployment #706)
   • uniswap-v2-sdk
   • ...

6. then rest of remaining small packages?

Maybe sounds a lot of work but this way we make sure there are less unrecognised bugs and if we find a bug its easy to find out to which thing it belongs? because sometimes really wired bug appear like #555 (comment) and hard to debug too

but lol maybe I am being too much cautious

Yes, I think it will be easier to do it that way. Starting to make these smaller prs

Also thinking about 7. Up yarn to last version (4.4.1 currently) but need to check stability, speed and so on, not sure it's worth it