-
Notifications
You must be signed in to change notification settings - Fork 944
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
Update and typescript version #499
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but I think it is better that @sverps looks at it before merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this solves the issues, we can merge this for now. I'll have a second look to see if there's an alternative, but no need to wait for that.
* Fix RainbowKitCustomConnectButton dropdown styles (#500) * chore: footer missalignment & home page on small screens (#502) Co-authored-by: CJ <[email protected]> * Update and typescript version (#499) * update typescript and viem version * update next config * fix: header links wrapping icons and text (#510) * Fix typos in useScaffoldContractWrite logs (#512) * fix: spelling in test file name (#522) * add suport for verify in foundry similar to hardhat * update git task title when using foundry * add changeset * update changeset --------- Co-authored-by: Rinat <[email protected]> Co-authored-by: CJ <[email protected]> Co-authored-by: Zak G <[email protected]>
Description
So after a lot of digging, I landed on how to two versions of same npm package and for some reason, I am not able to find that particular link but people were trying to have kind of same typescript version. Which led to me thinking that the reason
yarn next:check-types
might be checkingnode_modules
as discussed in #492 is becauseviem
is using typescript version5+
So the steps I followed to fix #492 :
Updated
viem
version to latest usingyarn workspace @se-2/nextjs up viem
I did
yarn next:check-types
here I got678 errors
mostly fromnode_modules/viem
yarn workspace @se-2/nextjs up typescript
(For some reason this also updated hardhat typescript version which is ok I think nd kind of makes sense)Again
yarn next:check-types
it now gave me only errors from Se-2 repo regardingAddressType
Updated
abi.d.ts
, to also handleviem/node_modules/abitype
and haveAddressType : string
Again
yarn next:check-types
and lol no types error at all!!Started with manual testing and found that nextjs app broke with "Cannot find
fs
module error", after some digging found this on Rainbowkit installation Page :So I added nextjs config which they linked on their installation Page and everything started working. I don't why we didn't have to do it before.
My wild guess is something heavily changed inside
viem
which kind of removed exposingethers
to outter world and we got that error becauseviem
is internally usingethers
somewhere, check its dependencies here.Lol I didn't particularly know what was actual cause, so explained all the steps if someone can infer something from it 🙌.
I need to do some testing nicely, will do it tomorrow and would appreciate it if others could test as well 🙌
Also please feel free to share your thoughts !!
Additional Information
Related Issues
#492
Your ENS/address: shivbhonde.eth