Skip to content

Frontend/build: Don't emit code while typechecking#8121

Merged
tristanlabelle merged 1 commit into
developfrom
frontend/task/typecheck-noemit
Mar 19, 2026
Merged

Frontend/build: Don't emit code while typechecking#8121
tristanlabelle merged 1 commit into
developfrom
frontend/task/typecheck-noemit

Conversation

@tristanlabelle

@tristanlabelle tristanlabelle commented Mar 18, 2026

Copy link
Copy Markdown
Contributor

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

  • There are no console warnings when running the app
  • Added tests where relevant
  • Clicked around my changes running locally and it works
  • Checked Desktop, Mobile and Tablet screen sizes

For maintainers

  • Maintainers can push commits to my branch
  • Maintainers can merge this PR for me

@vercel

vercel Bot commented Mar 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
couchers Ready Ready Preview Mar 18, 2026 7:55am

Request Review

@tristanlabelle
tristanlabelle merged commit 6164c66 into develop Mar 19, 2026
12 checks passed
@tristanlabelle
tristanlabelle deleted the frontend/task/typecheck-noemit branch March 19, 2026 09:03
@github-actions

Copy link
Copy Markdown
Contributor

📝 Release Notes

This 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 Information

Model: couchers.openai.gpt-5.4
Decision: exclude
Reasoning: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants