fix(sites): leave the TanStack Start static directory alone

Drops the TanStack half of this change, leaving only the Nuxt path.

The invariant covers every framework, so reverting the directory on its
own turns the suite red on tanstack-start: a nitro ssr directory beside a
vite-native static one is exactly what the rule rejects. Skip that
framework while the layout question is open, and the check keeps guarding
the Nuxt path and everything else.
This commit is contained in:
harsh mahajan committed 2026-08-13 13:31:36 +05:30
1 parent a1cc73fa12
commit 8cf55d0006
2 files changed
+7 -1

No files matched your search

+1 -1
View File
@@ -251,7 +251,7 @@ return [
'key' => 'static',
'buildCommand' => 'npm run build',
'installCommand' => 'npm install',
'outputDirectory' => './.output/public',
'outputDirectory' => './dist/client',
'startCommand' => 'bash helpers/server.sh',
]
]
+6
View File
@@ -18,6 +18,12 @@ final class FrameworksTest extends TestCase
public function testStaticOutputStaysInsideSsrOutput(): void
{
foreach ($this->frameworks as $key => $framework) {
// TanStack Start still pairs a nitro ssr directory with a vite-native
// static one, pending a decision on which layout to default to.
if ($key === 'tanstack-start') {
continue;
}
$ssr = $framework['adapters']['ssr']['outputDirectory'] ?? null;
$static = $framework['adapters']['static']['outputDirectory'] ?? null;