refactor(types): cleanup types / useless expression #74270
+56
−62
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.
For Contributors
Improving Documentation
pnpm prettier-fix
to fix formatting issues before opening the PR.For Maintainers
What?
I refactored some any types in build file, because it's too hard to know what original typed in huge project.
and added
typedEntries
lib for better type inference thanObject.entries
. When if you keep key/value pair type as constantly, i think it's useful.Why?
How?