TanStack Start is now the default for new apps

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want TanStack Start is now the default for new apps working in a real project rather than a sandbox.

   Set up TanStack Start is now the default for new apps in this project — faster web apps from the start with default server-side rendering. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Launch a new app with server-side rendering enabled by default

   The record lists this as one of the jobs TanStack Start is now the default for new apps is meant for, so it is a fair first test of whether it fits your app.

   In this project, use TanStack Start is now the default for new apps for launch a new app with server-side rendering enabled by default. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   TanStack Start is now the default for new apps is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses TanStack Start is now the default for new apps before I publish. Check default server-side rendering and better SEO from launch, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Get better SEO out of the box on a freshly created project

   A second job the record lists for TanStack Start is now the default for new apps, useful once the first path works.

   Extend this project so TanStack Start is now the default for new apps also covers get better SEO out of the box on a freshly created project. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is TanStack Start is now the default for new apps?

  TanStack Start is now the default for new apps is Lovable's Workflow feature: Faster web apps from the start with default server-side rendering. New apps created from this date will default to TanStack Start with server-side rendering enabled.

• Is TanStack Start is now the default for new apps GA or in beta?

  TanStack Start is now the default for new apps is generally available (GA) on Lovable.

• What Lovable plan includes TanStack Start is now the default for new apps?

  TanStack Start is now the default for new apps is available on all Lovable plans.

• When did TanStack Start is now the default for new apps launch?

  TanStack Start is now the default for new apps launched on May 18, 2026.

• Build and Plan mode switchSame category, also GA · May 2026
• Workspace skillsSame category, also GA · May 2026
• Cleaner inbox notificationsSame category, also GA · Jun 2026