Closed rin-st closed 3 weeks ago
Lol I am afraid and procrastinating to test this
Probably we could have divided this in to :
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 https://github.com/scaffold-eth/scaffold-eth-2/pull/555#issuecomment-1745081772 and hard to debug too
but lol maybe I am being too much cautious
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
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 🤷‍♂️
Last react-query
version 5.53.1
(3 hours ago) breaks requests with BigInt
s 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
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
Lol I am afraid and procrastinating to test this
Probably we could have divided this in to :
- updating Wagmi , Viem, Abitype, Rainbowkit versions
- Next, react, react-dom all realted package versions
- Typescript, eslint, eslint typescript etc versions
- Hardhat updagrades
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
- ...
- 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
Nextjs still doesn't support eslint v9, so skipping step 3 for now https://github.com/vercel/next.js/issues/64409 , but I think up TS version later. See also https://github.com/scaffold-eth/scaffold-eth-2/pull/905
Resolved, see referenced PRs
Description
react-copy-to-clipboard
types definition since after updates types breakshusky
script and pre-commit. See "How to migrate" block https://github.com/typicode/husky/releases/tag/v9.0.1nextjs/out
folder from formattingAdds 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:
Tried all the scripts from root package.json and looks like everything works as expected
Additional Information