Docs / Reference

Compatibility Matrix

Check whether Better Fullstack options work with a selected baseline stack.

Better Fullstack validates stack choices before generation. The builder, CLI, and MCP server use the same compatibility logic, so invalid combinations are rejected or adjusted consistently.

Check a Stack Combination

Start from a default baseline, adjust the key fields, then inspect one option category.

Ecosystem

Baseline Stack

These fields affect compatibility for the selected category.

FrontendBackendRuntimeDatabaseORMAPIAuthCSSUI library

Category to inspect

Option	Status	Notes
Tanstack Router tanstack-router	Compatible	No compatibility issues found.
React Router react-router	Compatible	No compatibility issues found.
React + Vite react-vite	Compatible	No compatibility issues found.
Tanstack Start tanstack-start	Compatible	No compatibility issues found.
Next.js next	Compatible	No compatibility issues found.
Vinext vinext	Compatible	No compatibility issues found.
Nuxt nuxt	Compatible	API set to 'oRPC' (required for this frontend) UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
SvelteKit svelte	Compatible	API set to 'oRPC' (required for this frontend) UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
Solid solid	Compatible	API set to 'oRPC' (required for this frontend) UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
Solid Start solid-start	Compatible	API set to 'oRPC' (required for this frontend) UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
Astro astro	Compatible	API set to 'oRPC' (tRPC requires React integration with Astro) UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
Qwik qwik	Compatible	UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
Angular angular	Compatible	UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
RedwoodJS redwood	Compatible	UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
Fresh fresh	Compatible	UI library changed to 'daisyUI' (React-only library incompatible with this frontend)
None none	Compatible	CSS framework set to 'None' (no web frontend) UI library set to 'None' (no web frontend)

What it checks

Whether an option is compatible with the selected baseline stack.
The shared disabled reason when a combination is blocked.
Any automatic adjustment notes from the same compatibility analyzer used by the builder.

How to use it

Pick an ecosystem.
Adjust the baseline stack fields that matter to your question.
Pick a category to inspect.
Review which options are compatible and why any are blocked.

This is a practical matrix, not every possible pairwise combination. For full project validation, run the CLI, use the Stack Builder, or call bfs_check_compatibility through MCP before scaffolding.

Compatibility behavior

none disables optional categories when supported.
Some selections trigger automatic adjustments, such as Convex replacing backend-owned database/API choices.
Some frontend choices intentionally narrow API, UI, runtime, or deploy support.
Java, Rust, Python, and Go use ecosystem-specific categories instead of the full TypeScript stack surface.