Skip to content
Source
Sign inSign up
TanStack/router

[@tanstack/react-start/plugin/rsbuild] tanstackStart() eclipses the client environment's output.assetPrefix, blocking downstream plugins #7827

Send to my agent
Openalexandre-marchina(GitHub profile, opens in a new tab) opened this issue 3 comments

Which project does this relate to?

Start

Describe the bug

tanstackStart() unconditionally writes assetPrefix to the client rsbuild environment in modifyRsbuildConfig. Because the environment override wins over the root value in rsbuild's merge, Start's write hides whatever the user (or a downstream plugin) had

Complete minimal reproducer

https://github.com/alexandre-marchina/tanstack-start-rsbuild-prefix-repro

Steps to Reproduce the Bug

In the repro above: npm run repro runs three configs (no user config with tanstackStart(), explicit output.assetPrefix with tanstackStart(), and a third without tanstackStart()) and prints the observed env override / effective / root values for each

Expected behavior

  • No output.assetPrefix and no server.base - Start writes nothing to the client environment
  • output.assetPrefix set - forwarded to the client environment
  • server.base set - takes precedence

Screenshots or Videos

No response

Platform

  • @tanstack/start-plugin-core: 1.168.x (latest)
  • @rsbuild/core: 2.1.5
  • @tanstack/react-start: 1.168.x
  • Environment: macOS, Node.js >= 20
  1. Complete minimal reproducer

    this is not a reproducer project

    also please don't paste a bunch of LLM output here. this is way too much noise.

  2. @schiller-manuel Sorry, pasted the wrong link https://github.com/alexandre-marchina/tanstack-start-rsbuild-prefix-repro

    Also trimmed the issue description

  3. I’m working on this issue. It looks like we need a clearer configuration workflow for Rsbuild that distinguishes between framework defaults, user-provided configuration, and framework-enforced values.

Sign in to join this conversation.