feat: add TanStack Start to framework list

[farisaziz12]

Context

TanStack Start as a framework has been gaining popularity (13.5K GH Stars). Based on that, it makes sense to add it to the homepage framework list.

I've picked the oklch color based on the --color-cyan-600 used on the TanStack Start page of the TanStack website.

Screenshots

Desktop

Mobile

CC: @tannerlinsley, @TkDodo, @schiller-manuel

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 15, 2026 10:48pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 15, 2026 10:48pm
npmx-lunaria	Ignored		Feb 15, 2026 10:48pm

[coderabbitai]

📝 Walkthrough

Walkthrough

A new framework entry for tanstack start is added to the SHOWCASED_FRAMEWORKS constant in app/utils/frameworks.ts. The entry includes the framework name, package identifier @tanstack/start, and a corresponding oklch colour value. This addition automatically updates the derived FrameworkPackageName union type. No modifications to existing logic, error handling, or other functionality are included.

Possibly related PRs

• feat: add solid to framework list #1288: Modifies the same SHOWCASED_FRAMEWORKS constant by adding a new framework entry, updating the FrameworkPackageName derived type.

Suggested reviewers

• ElianCodes
• danielroe

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description clearly explains the motivation for adding TanStack Start to the framework list, references its growing popularity with GitHub stars, details the colour choice based on TanStack's website, and includes supporting screenshots.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

app/utils/frameworks.ts (1)

73-75: Optional: Consider a type-safe alternative to the non-null assertion.

The ! assertion is safe in practice because FrameworkPackageName is derived from the same array, but the coding guidelines emphasise strictly type-safe code. A minor refactor could eliminate the assertion.

♻️ Type-safe alternative

 export function getFrameworkColor(framework: FrameworkPackageName): string {
- return SHOWCASED_FRAMEWORKS.find(f => f.package === framework)!.color+ const found = SHOWCASED_FRAMEWORKS.find(f => f.package === framework)+ if (!found) {+ throw new Error(`Framework not found: ${framework}`)+ }+ return found.color
}

As per coding guidelines: "Ensure you write strictly type-safe code, for example by ensuring you always check when accessing an array value by index".

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[tannerlinsley]

LGTM

[schiller-manuel]

this is not using the correct package.

@tanstack/react-start
@tanstack/solid-start

(and soon vue)

are the correct packages here

@tanstack/start is stale

[farisaziz12]

this is not using the correct package.

@tanstack/react-start

@tanstack/solid-start

(and soon vue)

are the correct packages here

@tanstack/start is stale

Thank you, @schiller-manuel. My bad! I'll open up a PR tomorrow to point to @tanstack/react-start