fix: resolve TypeScript type errors (claude code) - #2
Open
awwwdev wants to merge 1 commit into
Open
Conversation
Fix structural type issues without using `any` or `as` type assertions (except for safe DOM element narrowing). Errors reduced from 53 to 28, with all remaining errors being missing npm package/module issues. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
anyor unsafeastype assertionsTest plan
pnpm check-typesand verify error count is 28 (down from 53)pnpm devand verify no runtime regressions🤖 Generated with Claude Code