router: Tanstack-start on Cloudflare: ServerFn not working with API routes

Which project does this relate to?

Start

Describe the bug

This probably is an issue only related to Cloudflare Workers

  1. Create an API route /api/test;
  2. In page /count, do the following:
  • Create a route loader. In loader, call serverFn const count = await getCountServerFn().
  • In getCountServerFn, simply fetch(${BASE_URL}/api/test)
  1. In local development, everything is ok. Soft navigation to /count, or do a hard refresh on /count, I can see the count number being rendered.
  2. Build preview, everything is still ok.
  3. Deploy to Cloudflare Works as is.
  4. On production, no matter do a soft navigation to /count or do a hard refresh, it will resulting an error.

Additional information(all in production): For simplicity I used page /count for illustration. Below you can see the actual page is /user/deprecated

  • Soft navigate to page:
Image Image
  • Hard refresh:
Image Image
  • API route itself seems fine. I can fetch this API point from frontend with no problem(fetch in useEffect).

Your Example Website or App

https://tanstack-start-on-workers-v0.tuxi.workers.dev/user/deprecated

Steps to Reproduce the Bug or Issue

As mentioned above

Expected behavior

I can call API routes just fine in serverFn on Cloudflare

Screenshots or Videos

As mentioned above

Platform

  • OS: Mac OS Sequoia 15.4.1
  • Browser: Chrome 137.0.7151.41
  • Version: 1.116.1

Additional context

/routes/user/deprecated.tsx

import { createFileRoute } from '@tanstack/react-router';
import { createServerFn } from '@tanstack/react-start';
import { BASE_URL } from '@/utils/base-url';

const getCountServerFn = createServerFn({ method: 'GET' }).handler(async () => {
  const res = await fetch(`${BASE_URL}/api/test`);
  if (!res.ok) {
    throw new Error(`api/test failed: ${res.status} ${res.statusText}`);
  }
  return res.json();
});

export const Route = createFileRoute('/user/deprecated')({
  loader: async ({ context }) => {
    const count = await getCountServerFn();

    return { count };
  },
  component: RouteComponent,
  errorComponent: () => <div>error</div>,
});

function RouteComponent() {
  const { count } = Route.useLoaderData();

  return (
    <div>
      <h2>
        <pre>{JSON.stringify(count, null, 2)}</pre>
      </h2>
    </div>
  );
}

/routes/api/test.ts

import { createAPIFileRoute } from '@tanstack/react-start/api';
import { Redis } from '@upstash/redis/cloudflare';

export const APIRoute = createAPIFileRoute('/api/test')({
  GET: async ({ request, params, env }) => {
    console.log('get test api', JSON.stringify(request));
    const redis = Redis.fromEnv(
      env ?? {
        UPSTASH_REDIS_REST_URL: 'xxx',
        UPSTASH_REDIS_REST_TOKEN: 'xxx',
      }
    );
    const count = await redis.incr('counter');
    return new Response(JSON.stringify({ count }));
  },
});

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Reactions: 1
  • Comments: 22 (4 by maintainers)

Most upvoted comments

@schiller-manuel Thanks. I haven’t tested with alpha yet. I’m waiting for it to be stable, and have documentation to read, it’s too hard to fix bugs without understanding exactly what they are 😁

cloudflare worker is implemented like you run javascript script once per request, they intercept all requests as callback to itself to avoid infinite loop, you can only do it when it is bound to a new worker (as per their docs that I can understand)

Worker A is your application (you can not call from A to A) Worker B is a new copy of A, if you want to make an end point call to /api/test

For example:

function mainA() {
    console.log(" this is worker A")
}


function mainB() {
    console.log(" this is worker B")
}
//Error will occur
//if:

function mainA() {
    console.log(" this is worker A")
    mainA()
}  //Infinite loop

//you can only do it by:
function mainB() {
    console.log(" this is worker B")
    mainA() //can only call A here
}