Something like buildLocation on the server

[CanRau]

There's currently nothing like buildLocation on the server side right?

I'm looking for the most ergonomic way to generate callbackUrls on the server, for things like Stripe, that are url rewrite aware etc for a multi tenant app. Ideally I'd have some buildLocation/linkOptions interface to construct those urls, maybe I'd just prefix the correct tenant's origin 🤔
linkOptions is of course available, but just a type helper.

I could also pass the buildLocation generated callbackUrl from the client to the server function, although I'd need to validate it and still think buildLocation would be really helpful on the server and simpler.

Any tips?

[abhayclasher]

yo, so buildLocation actually works on the server too if u got the router instance handy. if ur using TanStack Start, u can just import ur router and call router.buildLocation({ to: '/wherever' }).href.

since ur doing multi-tenant with Stripe, u probs just need the path string to slap onto ur tenant origin. linkOptions is great for the types, but yeah, router.buildLocation is the one that actually spits out the URL object with the href. just make sure ur server-side router config matches ur client one so the rewrites/basepaths don't get wonky. ✌️

[CanRau]

Hmm, tried in start.ts and an actual route file (API route, server.handlers.GET) but get
TypeError: Cannot read properties of undefined (reading 'pathname') at Router.matchRoutesLightweight

imported like so import { getRouter } from "~/router";

Tried a dynamic to and a static route 🤔

[uncvrd]

@CanRau Struggling to get this to work too...I have a server side method that needs to run outside of the Start context which means I don't have access to the getRouterInstance() like I normally do to call buildLocation. I tried creating a server only memory router

let serverRouter: ReturnType<typeof getRouter> | null = null;

export const getServerRouter = () => {
	if (!serverRouter) {
		serverRouter = getRouter();

		serverRouter.update({
			context: getContext(),
			history: createMemoryHistory({ initialEntries: ["/"] }),
		});
	}

	return serverRouter;
};

but since getRouter imports the routerTree.gen.ts and this imports __route.tsx , and my __route.tsx file contains a .css import, when I run a server side tsx script, the script chokes on the .css file...I just want to build a route...a little stuck

~/apps/web$ tsx --env-file=.env ./dbos/server.ts ⊘ cache disabled

node:internal/modules/run_main:107
    triggerUncaughtException(
    ^
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".css" for /root/GitHub/foundry/workspace/apps/web/src/styles/globals.css
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:185:9)
    at defaultGetFormat (node:internal/modules/esm/get_format:211:36)
    at defaultLoad (node:internal/modules/esm/load:94:16)
    at nextLoad (node:internal/modules/esm/hooks:785:28)
    at load (file:///root/GitHub/foundry/workspace/node_modules/.pnpm/tsx@4.20.6/node_modules/tsx/dist/esm/index.mjs?1774976675324:2:1777)
    at nextLoad (node:internal/modules/esm/hooks:785:28)
    at AsyncLoaderHooksOnLoaderHookWorker.load (node:internal/modules/esm/hooks:410:26)
    at handleMessage (node:internal/modules/esm/worker:251:24)
    at Immediate.checkForMessages (node:internal/modules/esm/worker:193:28)
    at process.processImmediate (node:internal/timers:504:21) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

Any luck on your end the past few weeks?

[AhmedBaset]

You can fix this error by replacing tsx with npx vite-node

[travisbreaks]

buildLocation crashes on the server because latestLocation is never initialized. The router skips createBrowserHistory() when isServer is true, so there's no history, no location, and matchRoutesLightweight blows up on undefined.pathname.

The fix is a dedicated lightweight server router with createMemoryHistory:

import { createMemoryHistory, createRouter } from '@tanstack/react-router'
import { routeTree } from '~/routeTree.gen'

const serverRouter = createRouter({ routeTree })
serverRouter.update({
  history: createMemoryHistory({ initialEntries: ['/'] }),
})

export function buildServerPath(opts) {
  return serverRouter.buildLocation(opts).href
}

Don't import your app's getRouter() for this; it depends on Start's per-request lifecycle and won't have a history instance outside the SSR render path. Keep basepath/rewrite settings in sync between the two routers.

Simpler alternative: build the URL on the client where the router is already initialized, pass it to the server function, and validate the origin server-side.