Skip to content
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

Upgrade to typescript v5 #4184

Merged
merged 4 commits into from
Jul 26, 2023
Merged

Upgrade to typescript v5 #4184

merged 4 commits into from
Jul 26, 2023

Conversation

fvictorio
Copy link
Member

@fvictorio fvictorio commented Jul 21, 2023

We'll need this to be able to use viem.

@alcuadrado important things here:

  • I'm using ~5.0.0 as the version range in all packages (even the toolbox).
  • This commit is the one that fixes the two compilation errors that showed up after upgrading.
  • I added a workflow to compile the whole repository with typescript v4. I also pushed a temporary commit to double-check that the workflow fails as expected (see here).

@changeset-bot
Copy link

changeset-bot bot commented Jul 21, 2023

⚠️ No Changeset found

Latest commit: 79f3941

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
Copy link

vercel bot commented Jul 21, 2023

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

Name Status Preview Comments Updated (UTC)
hardhat ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 21, 2023 9:46am
hardhat-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 21, 2023 9:46am

@alcuadrado
Copy link
Member

I think the workflow is overly restrictive. I believe that what we want is to check is that Hardhat's generated .d.ts are still compatible with TS 4.x, that's not the same as the sources being compatible.

@fvictorio
Copy link
Member Author

@alcuadrado that makes sense, but since it's passing, do you mind if we merge it? I think testing this properly would require e2e tests. I can update the e2e issue to include that, and we can remove that workflow when we do it.

@alcuadrado
Copy link
Member

sure!

@fvictorio fvictorio merged commit 06d7308 into main Jul 26, 2023
140 of 175 checks passed
@fvictorio fvictorio deleted the upgrade-to-ts-5 branch July 26, 2023 07:59
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
no changeset needed This PR doesn't require a changeset status:ready This issue is ready to be worked on
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants