GeezerVison is showing github.com — fix(create): align Biome formatter with starter files by tannerlinsley · Pull Request #577 · TanStack/cli
Conversation
tannerlinsley
commented
Nov 8, 2026
•
edited by coderabbitai
Bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
Fresh Biome starters now use two spaces, single quotes, and semicolons only where needed. The generated config also passes its own formatter.
Verified Biome 2.4.5 format and lint in fresh standard and blank React and Solid apps outside the repo. The create package build and type compilation passed.
Fixes #576.
Summary by CodeRabbit
- New Features
- Generated React and Solid starter projects now apply Biome formatting settings based on the selected TypeScript formatting preference. TypeScript formatting uses two-space indentation, single quotes, and omits unnecessary semicolons; other projects use tabs and double quotes.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
changeset-bot
Bot
commented
Nov 8, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
coderabbitai
Bot
commented
Nov 8, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|

Walkthrough
-
The template renderer now provides formatsTypeScript to generated templates. React and Solid starter Biome configurations use that value to select formatting options. A changeset records a patch release for @tanstack/create.
Changes: Starter Biome Defaults
| Layer / File(s) |
Summary |
Wire formatting options into starter templates packages/create/scripts/generate-manifest.mjs, packages/create/src/template-file.ts, packages/create/src/frameworks/react/toolchains/biome/assets/biome.json.ejs, packages/create/src/frameworks/solid/toolchains/biome/assets/biome.json.ejs, .changeset/biome-starter-format.md |
The generated render context declares optional formatsTypeScript, and template rendering sets it to true. The React and Solid Biome templates use the value to select indentation, quote style, and semicolon settings. The React template removes an empty bundler conditional. The changeset records a patch release for @tanstack/create. |
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Bug fix · Severity of issue fixed: Low
Suggested reviewers: schiller-manuel
Merge Risk: Minimal · up to d0f83
-
Node-generated starters use the updated Biome settings, while edge generation retains its previous defaults. No merge-blocking risk was identified.
Pre-merge checks: 4 · 1
-
Failed checks: 1 warning
| Check name |
Status |
Explanation |
Resolution |
| Docstring Coverage |
 |
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… |
Write docstrings for the functions missing them to satisfy the coverage threshold. |
Passed checks: 4 passed
-
| Check name |
Status |
Explanation |
| Description Check |
 |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check |
 |
The title "fix(create): align Biome formatter with starter files" matches the main change. The changeset updates the Biome templates for React and Solid so the generated biome.json uses two-space inde… |
| Linked Issues check |
 |
Issue #576 requires generated Biome config to match the starter files: two-space indentation, single quotes, and no unnecessary semicolons. At the reviewed head, the React template packages/create/src… |
| Out of Scope Changes check |
 |
The whole-PR changes are: the React and Solid biome.json.ejs templates, packages/create/src/template-file.ts (adds formatsTypeScript: true to templateValues), packages/create/scripts/generate-manifest… |
Full details: Title check
-
Explanation
The title "fix(create): align Biome formatter with starter files" matches the main change. The changeset updates the Biome templates for React and Solid so the generated biome.json uses two-space indentation, single quotes, and semicolons only where needed, matching the starter files. The title names the package, the Biome formatter, and the starter files, which are the core of the change. The linked issue #576 describes the same mismatch between starter files and biome.json.
Full details: Linked Issues check
-
Explanation
Issue #576 requires generated Biome config to match the starter files: two-space indentation, single quotes, and no unnecessary semicolons. At the reviewed head, the React template packages/create/src/frameworks/react/toolchains/biome/assets/biome.json.ejs sets formatter.indentStyle to "space" with indentWidth 2, javascript.formatter.quoteStyle to "single", and javascript.formatter.semicolons to "asNeeded" when formatsTypeScript is truthy. The whole-PR diff of packages/create/src/template-file.ts adds formatsTypeScript: true to templateValues, so generated apps take this branch. The previous review used hard-coded values. This head replaces them with a formatsTypeScript conditional, so the previous reasoning is revised. The Solid template was not read at this head because the inspection budget was used. Its settings rest on the change summary, which reports the same conditional values. The PR's manual Biome 2.4.5 check was not re-run. No automated test is required by the issue, which is a template configuration requirement.
Full details: Out of Scope Changes check
-
Explanation
The whole-PR changes are: the React and Solid biome.json.ejs templates, packages/create/src/template-file.ts (adds formatsTypeScript: true to templateValues), packages/create/scripts/generate-manifest.mjs (adds optional formatsTypeScript to the generated render context and TemplateRenderContext type), and a patch changeset for @tanstack/create. The formatsTypeScript plumbing is needed for the template conditionals that implement #576, so it connects to the issue. The React template no longer has the trailing empty bundler conditional. This is cleanup in a file already changed for #576 and does not change generated output. The changeset documents the template change. The generate-manifest.mjs change is known from the summary only, because the source diff was unavailable. Its behavior is not independently verified. No change was found that lacks a connection to #576.
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 2 functions across 2 files. (2 skipped: 2 unsupported.)
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
Finishing Touches
-
Generate docstrings
-
- Commit to this branch
- Create a new PR
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Share
-
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Reviewers
At least 0 approving reviews are required to merge this pull request.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
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.
|