Needs a static export
How to publish a TanStack Start site as a static export
TanStack Start builds a server bundle rather than a finished site, so it needs to be exported as static first, if your setup allows it at all.
It builds its pages on a live server each time someone visits, and Droply publishes finished pages, so there is nothing here for us to put online yet. In the tool you built it with, look for an option like "static site", "static export" or "SPA" and export it that way, then upload the folder you get.
Free plan, free SSL, no credit card.
-
Export it as a static site
It builds its pages on a live server each time someone visits, and Droply publishes finished pages, so there is nothing here for us to put online yet. In the tool you built it with, look for an option like "static site", "static export" or "SPA" and export it that way, then upload the folder you get.
-
Check for an index.html
Open the folder you got. If there is no index.html in it, the export produced a server bundle and there is nothing to publish yet.
-
Upload the folder
Drag it into Droply and the site is live on an HTTPS droply.id subdomain in seconds.
Worth knowing about TanStack Start
A TanStack Start build produces no index.html at all, which is why uploading it fails with nothing found rather than with a partial site.
In the tool you built it with, look for a "static site", "static export" or "SPA" option and export it that way.
This is the exact case that made us detect frameworks by name: the generic advice would have sent you round the same loop twice.
Did an AI tool build this project?
Hosting an AI-generated website covers the question that comes before the build command: whether what you are holding is a single file or a project, and which of the two every tool actually hands back.