Repository navigation
chore: upgrade Bun to 1.4.3 and type check with bun check - #598
Merged
kianbazza merged 1 commit intoOct 10, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Summary
Bun 1.4.3 ships
bun check, a type checker ported from TypeScript 7.0.2 (the version the repo pins). It reads the sametsconfig.jsonand reports the same errors astsc. This moves the repo and CI to 1.4.3 and swaps thetype-checkscripts over.apps/webhas its owncheckscript (Biome), andbun checkruns a package'scheckscript when one exists.bun --checkalways means the type checker.typescriptstays installed for editors and the.d.tsbuilds.Evidence
Same result as
tscin every package, measured oncanarybefore the switch (wall time):tsc --noEmitbun checkapps/playground-nextjsapps/webpackages/filterspackages/reacttooling/lint(TS 5.9)apps/webandapps/playground-nextjssetincremental, so a warm localtscreusestsconfig.tsbuildinfoand is about as fast asbun check, which keeps no cache. CI always starts cold.A type error still fails the script, including in
apps/web:Merge Danger
Door: two-way
Reverting the commit restores
tscand Bun 1.3.11.Blast Radius: releases
The publish workflows run
bun publishon 1.4.3 from the next canary.ci:publishandci:publish:canaryend eachbun publishwith|| true, so a failed publish would not fail the job. Check that the first canary after this merge reaches npm.Closes UI-653