Frontend/build: Don't emit code while typechecking#8121
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WouldYouKindly
approved these changes
Mar 19, 2026
Contributor
📝 Release NotesThis PR does not need to be included in release notes. Reason: This PR only changes the frontend typecheck command to avoid emitting build artifacts during type checking. It's a developer workflow/build optimization with no user-facing impact and not a major infrastructure change that end users would notice. 🤖 Bot Debug InformationModel: |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type-checking doesn't require emitting code. It might make the operation faster, or at least it won't write files we don't need to the disk.
Testing
Introduced a type error locally and ran
yarn typecheck.Web frontend checklist
For maintainers