Skip to content
Source
Sign inSign up
TanStack/router

Start SSR bundle calls createServerFn before initialization with pnpm symlinked layout #8139

Send to my agent
Openastelmach20(GitHub profile, opens in a new tab) opened this issue 1 comment

Which project does this relate to?

Start

Describe the bug

A small TanStack Start SSR app builds successfully but returns HTTP 500 on every request when installed with pnpm's default symlinked node_modules layout. The emitted .output/server/_ssr/ssr.mjs invokes createServerFn before its assignment:

TypeError: createServerFn is not a function
    at .output/server/_ssr/ssr.mjs:40:18

The same source and exact dependency versions return HTTP 200 when installed with a hoisted layout. The trigger is importing a Drizzle pgTable schema into the server-function/query graph. Removing that schema import also makes the symlinked build work.

The divergence begins in Nitro's intermediate Vite build:

InstallLayoutHTTPIntermediate SSR entryFinal ssr.mjs
pnpm installsymlinked500247.04 kB242.49 kB
pnpm install --config.node-linker=hoistedhoisted20066.89 kB64.72 kB

This was independently controlled with Bun as well: Bun's isolated layout has the same failure and its hoisted layout succeeds. Because pnpm reproduces the failure without Bun, the behavior follows the dependency layout and appears to be in the TanStack Start / Nitro bundling pipeline.

Complete minimal reproducer

https://github.com/astelmach20/tanstack-start-symlink-layout-repro

The repository contains no application code, credentials, or private dependencies. A database is not required; the module fails during SSR startup before the sample database URL can be used.

Steps to reproduce

git clone https://github.com/astelmach20/tanstack-start-symlink-layout-repro.git
cd tanstack-start-symlink-layout-repro
corepack enable
pnpm install --frozen-lockfile
pnpm build
pnpm preview
curl -i http://127.0.0.1:4173/

The build exits 0, then the request returns HTTP 500 with createServerFn is not a function.

Hoisted control from a second clean clone:

pnpm install --frozen-lockfile --config.node-linker=hoisted
pnpm build
pnpm preview --port 4174
curl -i http://127.0.0.1:4174/

This returns HTTP 200.

Expected behavior

The generated SSR bundle should preserve module initialization order under pnpm's supported default layout, or the build should fail instead of emitting a bundle that cannot serve a request.

Platform

  • @tanstack/react-start: 1.168.28
  • @tanstack/react-router: 1.170.18
  • @tanstack/react-router-ssr-query: 1.167.1
  • @tanstack/react-query: 5.101.2
  • nitro: 3.0.260610-beta
  • vite: 8.1.5
  • drizzle-orm: 0.45.2
  • postgres: 3.4.9
  • react / react-dom: 19.2.7
  • pnpm: 10.17.1
  • Node: 23.7.0
  • OS: macOS arm64; the equivalent isolated-layout failure was also observed in a Linux serverless runtime
  • Bundler: Vite / Nitro (node-server preset)

Additional context

  1. I bisected this using the reproducer linked above. With symlinked pnpm, the result tracks the Rolldown version; Start and Nitro versions do not change it.

    Setupsymlinkedhoisted
    versions from the report (frozen lockfile; Vite 8.1.5, Rolldown 1.1.5)500 createServerFn is not a function200
    only @tanstack/react-start + @tanstack/react-router bumped to 1.169.4 / 1.170.46500—
    only nitro bumped to 3.0.261103-rc500—
    Vite 8.2.4 (Rolldown 1.2.5)500—
    Vite 8.2.4 + pnpm.overrides Rolldown 1.2.6 / 1.2.7 / 1.2.12 / 1.2.13 / 1.2.14 / 1.2.15500—
    Vite 8.2.4 + pnpm.overrides Rolldown 1.2.16200—
    Vite 8.3.0 or 8.3.5 (Rolldown 1.2.16)200200

    Each run was pnpm build, then node .output/server/index.mjs, then curl /. Node 24.22.1, pnpm 10.17.1.

    So, on this reproducer, the bug goes away with Rolldown 1.2.16, released 2026-10-29. I did not bisect commit by commit. These 1.2.16 changes look like the likely fix:

    Note that vite@^8.3.0 asks for rolldown ~1.2.6. An existing lockfile can keep an affected 1.2.x patch, so it may be worth pinning rolldown >= 1.2.16 until this is confirmed.

    On current versions, the reproducer itself needs one change: useSession is no longer exported from @tanstack/react-start/server in 1.169.x. I swapped it for getCookie and kept the same dynamic import. With the report versions, that change does not hide the bug.

Sign in to join this conversation.