Welcome to your new TanStack Start app!

Getting Started

To run this application:

pnpm install
pnpm dev

Building For Production

To build this application for production:

pnpm build

Deploying to Cloudflare

This application is a client-side Vite SPA. The production build is written to dist, and VITE_API_URL must be available when the application is built. Use the public URL of the backend without a trailing slash, for example:

VITE_API_URL=https://api.example.com

VITE_* values are bundled into the browser application. Do not use them for secrets. The backend must also allow browser requests from the deployed *.pages.dev, *.workers.dev, or custom domain through its CORS configuration.

Option 1: Cloudflare Pages (recommended)

Deploy automatically from GitHub

1. Open the Cloudflare dashboard and go to Workers & Pages.
2. Select Create application > Pages > Import an existing Git repository.
3. Select the Devscale-Indonesia/agent-frontend repository.
4. Configure the deployment:
   • Production branch: main
   • Build command: pnpm build
   • Build output directory: dist
5. Under Environment variables, add VITE_API_URL with the production API URL. Add it to both Production and Preview if preview deployments need the API.
6. Select Save and Deploy.

Cloudflare Pages automatically rebuilds the application after commits are pushed to the configured branch. Because the build contains index.html and does not contain a top-level 404.html, Pages treats it as an SPA and serves index.html for client-side routes such as /login and /s/:sessionId.

Deploy to Pages from the CLI

Authenticate and create the Pages project once:

npx wrangler login
npx wrangler pages project create

When prompted, use agent-frontend as the project name and main as the production branch. Then build and deploy:

VITE_API_URL=https://api.example.com pnpm build
npx wrangler pages deploy dist --project-name=agent-frontend --branch=main

Run the build and deploy commands again whenever a new version should be published.

Option 2: Cloudflare Workers Static Assets

Workers can serve this SPA directly without a Worker script. Create a wrangler.jsonc file in the project root:

{
  "$schema": "node_modules/wrangler/config-schema.json",
  "name": "agent-frontend",
  "compatibility_date": "2026-07-13",
  "assets": {
    "directory": "./dist",
    "not_found_handling": "single-page-application"
  }
}

The single-page-application setting makes unmatched navigation requests serve index.html, which is required for TanStack Router routes opened directly or refreshed in the browser.

Authenticate, build, and deploy:

npx wrangler login
VITE_API_URL=https://api.example.com pnpm build
npx wrangler deploy

Wrangler prints the generated *.workers.dev URL after deployment. For later deployments, rebuild with the correct VITE_API_URL and run npx wrangler deploy again.

Cloudflare references:

• Deploy a Vite project to Pages
• Pages Direct Upload with Wrangler
• Workers Static Assets
• Workers SPA routing

Testing

This project uses Vitest for testing. You can run the tests with:

pnpm test

Styling

This project uses Tailwind CSS for styling.

Removing Tailwind CSS

If you prefer not to use Tailwind CSS:

1. Remove the demo pages in src/routes/demo/
2. Replace the Tailwind import in src/styles.css with your own styles
3. Remove tailwindcss() from the plugins array in vite.config.ts
4. Uninstall the packages: pnpm add @tailwindcss/vite tailwindcss --dev

Linting & Formatting

This project uses Biome for linting and formatting. The following scripts are available:

pnpm lint
pnpm format
pnpm check

Routing

This project uses TanStack Router with file-based routing. Routes are managed as files in src/routes.

Adding A Route

To add a new route to your application just add a new file in the ./src/routes directory.

TanStack will automatically generate the content of the route file for you.

Now that you have two routes you can use a Link component to navigate between them.

Adding Links

To use SPA (Single Page Application) navigation you will need to import the Link component from @tanstack/react-router.

import { Link } from "@tanstack/react-router";

Then anywhere in your JSX you can use it like so:

<Link to="/about">About</Link>

This will create a link that will navigate to the /about route.

More information on the Link component can be found in the Link documentation.

Using A Layout

In the File Based Routing setup the layout is located in src/routes/__root.tsx. Anything you add to the root route will appear in all the routes. The route content will appear in the JSX where you render {children} in the shellComponent.

Here is an example layout that includes a header:

import { HeadContent, Scripts, createRootRoute } from '@tanstack/react-router'

export const Route = createRootRoute({
  head: () => ({
    meta: [
      { charSet: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { title: 'My App' },
    ],
  }),
  shellComponent: ({ children }) => (
    <html lang="en">
      <head>
        <HeadContent />
      </head>
      <body>
        <header>
          <nav>
            <Link to="/">Home</Link>
            <Link to="/about">About</Link>
          </nav>
        </header>
        {children}
        <Scripts />
      </body>
    </html>
  ),
})

More information on layouts can be found in the Layouts documentation.

Server Functions

TanStack Start provides server functions that allow you to write server-side code that seamlessly integrates with your client components.

import { createServerFn } from '@tanstack/react-start'

const getServerTime = createServerFn({
  method: 'GET',
}).handler(async () => {
  return new Date().toISOString()
})

// Use in a component
function MyComponent() {
  const [time, setTime] = useState('')
  
  useEffect(() => {
    getServerTime().then(setTime)
  }, [])
  
  return <div>Server time: {time}</div>
}

API Routes

You can create API routes by using the server property in your route definitions:

import { createFileRoute } from '@tanstack/react-router'
import { json } from '@tanstack/react-start'

export const Route = createFileRoute('/api/hello')({
  server: {
    handlers: {
      GET: () => json({ message: 'Hello, World!' }),
    },
  },
})

Data Fetching

There are multiple ways to fetch data in your application. You can use TanStack Query to fetch data from a server. But you can also use the loader functionality built into TanStack Router to load the data for a route before it's rendered.

For example:

import { createFileRoute } from '@tanstack/react-router'

export const Route = createFileRoute('/people')({
  loader: async () => {
    const response = await fetch('https://swapi.dev/api/people')
    return response.json()
  },
  component: PeopleComponent,
})

function PeopleComponent() {
  const data = Route.useLoaderData()
  return (
    <ul>
      {data.results.map((person) => (
        <li key={person.name}>{person.name}</li>
      ))}
    </ul>
  )
}

Loaders simplify your data fetching logic dramatically. Check out more information in the Loader documentation.

Demo files

Files prefixed with demo can be safely deleted. They are there to provide a starting point for you to play around with the features you've installed.

Learn More

You can learn more about all of the offerings from TanStack in the TanStack documentation.

For TanStack Start specific documentation, visit TanStack Start.