skip to content

Lovable projects created in January 2026 and August 2026 — which stack does each run on, and what does upgrading the older one change?

level: juniorimportance: should knowfreq 5%

answer

  1. the default template moved in 2026
  2. server rendering versus browser rendering
  3. May 13, 2026 for new projects
  4. a migrate action, confirmed first
  5. live site waits for publish

basics

~20 s

The January project runs Lovable's older React + Vite stack; the August one runs TanStack Start, the default for new projects since May 13, 2026. Upgrading converts pages to server-side rendering; the live site changes only on the next publish.

solid answer

~50 s

Lovable made **TanStack Start** with server-side rendering the default for new projects on **May 13, 2026** (June 22, 2026 for new Enterprise projects), so the August project uses it and the January project is on the older **React + Vite** stack, which renders in the browser. An older project keeps working and can be upgraded in place with **Migrate to TanStack Start** — from `/` in the chat, from project settings, or by asking — after a confirmation. Lovable converts the page structure, carries over design, content, page metadata and backend code only the app uses, keeps externally called backend endpoints at their addresses, leaves the database untouched, and builds and loads every page to check it. The published site keeps serving the old version until you publish again, and the upgrade can be reverted from version history.

go deeper

for a junior

Remember the date: new Lovable projects use TanStack Start with server-side rendering from May 13, 2026; older ones are React + Vite and can be upgraded in place.

for a middle

Explain what the migration converts, what it leaves alone (the database, externally called endpoints, the live site until publish) and how to revert it from version history.

for a senior

Plan an upgrade for a live app: test pages that use browser-only libraries, check hosting outside Lovable now needs a server, and expect local runs to lose connector and AI calls.

for a principal

Judge whether an older app should migrate at all, weighing search visibility and newer features against regression risk, credit cost and any external hosting that assumes static files.

## Which stack a Lovable project is on Lovable generates a web app from a template, and the template changed in 2026: | | Older projects | Newer projects | |---|---|---| | Stack | **React + Vite** | **TanStack Start** | | Rendering | Browser builds the page with JavaScript | **Server-side rendering (SSR)**: finished HTML per request | | Default for new projects | Until May 13, 2026 | From **May 13, 2026**; new Enterprise projects from **June 22, 2026** | | Build output | Static files | Server code plus static files | So a project created in January 2026 is React + Vite and one created in August 2026 is TanStack Start, whatever the plan. If you are unsure, the docs suggest simply asking Lovable "What stack is this project on?". **Server-side rendering** means the server turns each page into complete HTML before sending it, so every visitor, search engine, AI crawler and link-preview bot receives the same finished page. A React + Vite app sends a mostly empty page that the visitor's browser fills in; Lovable compensates by serving pre-rendered copies of published pages to verified search engines and social preview bots, but tools outside that list see very little. ## Why the stack matters day to day - **Hosting elsewhere**: a React + Vite app builds to static files any static host can serve; a TanStack Start app runs server code (SSR, server functions, API routes) and needs a host that runs it. - **Features**: some newer Lovable features need TanStack Start, such as workspace identity reuse and live voice conversations in the app's AI features. - **Working locally**: in a TanStack Start app the server code runs on your own machine when you run the app locally, so calls that depend on Lovable-managed connector and AI credentials fail there; in a React + Vite app those calls run in edge functions on the Cloud backend. - **Payments with your own Supabase**: built-in payments on React + Vite apps require the built-in Cloud backend; newer TanStack Start apps (created from May 13, 2026) can use them with your own Supabase project. ## Upgrading an older project The upgrade is optional — React + Vite projects keep working — and happens inside the existing project. Anyone who can edit the project can start it, on any plan, in three ways, each asking for confirmation: 1. In the project chat, type `/` and choose **Migrate to TanStack Start**. 2. In project settings, under **General → Project actions**, select **Migrate**. 3. Ask Lovable in your own words; it replies with a **Migrate to TanStack Start** card with **Start migration** and **Cancel**. During the run Lovable inventories the pages (including those behind sign-in or admin checks, so the protection carries over), converts the page structure, moves titles, descriptions, social tags and analytics scripts, carries theme customisations, moves backend code only the app itself uses, and then builds the project and loads every page. Backend code that **outside services call directly** — a payment provider's webhook, a scheduled job, a connected AI assistant — keeps its web address so integrations need no reconfiguration. The **database is untouched**. The upgrade counts as build usage and consumes credits. ## What it does not change, and what can go wrong - **The live site**: visitors keep seeing the last published version until you publish again. - **Reversibility**: restore the pre-upgrade version from the project's version history; the published site was never touched. - **Browser-only libraries**: some libraries break server rendering in ways the upgrade's checks do not catch, so test pages afterwards and report any that fail to load. - **Installed PWAs**: devices that installed the app keep a saved copy of the old version; Lovable usually clears it for returning visitors and says when a manual follow-up is needed. - **One at a time**: one upgrade runs per project; a large project may pause partway and resume when asked. If you cannot find the migrate option at all, the project is probably already on TanStack Start or Lovable cannot determine its stack; asking Lovable which stack the project uses settles it. The framework itself — routing, server functions, how SSR works in TanStack Start — is a subject of its own; what matters here is which template Lovable gave the project and what Lovable's migration does to it.

  • After upgrading a Lovable project to TanStack Start, why might link previews still look wrong?
    The upgrade changes the project, not the live site. Until you publish the upgraded version, visitors and preview bots still get the old React + Vite build. Platforms also cache link previews for a while, so after publishing you re-check the link with the platform's preview debugger.
  • What happens to a payment provider's webhook endpoint when a Lovable project is upgraded to TanStack Start?
    It stays where it runs today. Lovable moves backend code that only the app itself calls into the new template, but code that outside services call at a fixed web address — webhooks, scheduled jobs, a connected AI assistant — keeps its address, so the integration keeps working without reconfiguration.

  • Every Lovable app is a React + Vite single-page app
  • Upgrading to TanStack Start immediately changes the published site
  • The TanStack Start upgrade migrates or resets the database
  • A Lovable TanStack Start app can be served from any static host
  • Old React + Vite projects must be upgraded or they stop working

Assumes Lovable's docs as fetched on 2026-10-04: TanStack Start has been the default template for new projects since May 13, 2026, and for new Enterprise projects since June 22, 2026.