mirror of
https://github.com/supabase/supabase.git
synced 2026-06-28 03:19:09 -04:00
9eab4f8fbf
**Stack 1/6** of the TanStack Start migration (#46424), split into reviewable, independently-mergeable PRs. > [!IMPORTANT] > **Next stays the default and only active framework after this PR.** This wires up the Vite/TanStack-Start build pipeline behind the `STUDIO_FRAMEWORK` flag, but there are no TanStack routes yet — so the TanStack build isn't functional or tested until later PRs in the stack. Nothing about the Next build, dev, or deploy changes behaviourally here. ## What's in this PR - **Dispatch:** `dev`/`build`/`start` now go through `scripts/dispatch.js`, which runs the Next variant unless `STUDIO_FRAMEWORK=tanstack`. The original commands are preserved as `dev:next`/`build:next`/`start:next`. - **Build pipeline:** `vite.config.ts`, `serve.js`, `smoke-server.mjs`, vite/tanstack deps, `turbo.jsonc`. - **`tsconfig.json`:** `jsx: react-jsx`, `moduleResolution: Bundler`, `target: ES2022`. Because `include` is `**/*.ts(x)`, this re-typechecks the whole app, so the companion adaptations below land with it. - **Shared adaptations (companions to the tsconfig change):** `BufferSource` casts, `packages/ui` unused-`React` import removals, etc. - **Routing/middleware plumbing:** `next.config.ts` + `redirects.shared.ts` (redirect rules now shared with `vercel.ts`), `proxy.ts`/`start.ts` middleware + `hosted-api-allowlist.ts`. ## Verification Run locally off `master`: frozen install ✓, `studio` typecheck ✓, **Next build ✓** (compiles + generates all routes), lint ratchet ✓ ("some rules improved"), prettier ✓. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a hosted API endpoint allowlist to return 404 for non-supported `/api/*` routes. * Introduced a TanStack route-migration checklist and expanded TanStack Start routing support. * **Improvements** * Enhanced deployment refresh/detection by tightening cookie handling for “latest deployment” updates. * Centralized redirect/maintenance-mode rules for consistent platform vs self-hosted behavior. * Improved production serving with a dedicated static + proxy server and a post-build smoke test. * **Dependencies** * Updated TanStack-related packages and React Table/query tooling versions. * **Documentation / Chores** * Updated formatting and tooling config; added shared build environment parsing utilities. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Alaister Young <[email protected]> Co-authored-by: Ivan Vasilov <[email protected]>
65 lines
2.5 KiB
JavaScript
65 lines
2.5 KiB
JavaScript
#!/usr/bin/env node
|
|
// Dispatch a top-level npm script (dev/build/start) to either the next- or
|
|
// tanstack-flavoured variant based on STUDIO_FRAMEWORK. We parse the env files
|
|
// (via the shared scripts/lib/env.js parser) and pull out only
|
|
// STUDIO_FRAMEWORK — we deliberately don't load the whole file into the
|
|
// child's process.env, because scripts/serve.js / vite do their own .env
|
|
// loading and would otherwise refuse to override the dispatcher-set values,
|
|
// including NEXT_PUBLIC_IS_PLATFORM which the e2e `.env.test` needs to flip to
|
|
// `false`.
|
|
//
|
|
// Usage: node scripts/dispatch.js <target>
|
|
// target ∈ { dev, build, start }
|
|
//
|
|
// Resolves to `pnpm run <target>:<framework>` where framework is `tanstack`
|
|
// when STUDIO_FRAMEWORK=tanstack (set in the shell env, `.env`, or
|
|
// `.env.local`), otherwise `next`.
|
|
import { spawn } from 'node:child_process'
|
|
import path from 'node:path'
|
|
import { fileURLToPath } from 'node:url'
|
|
|
|
import { readEnvFiles } from './lib/env.js'
|
|
|
|
const target = process.argv[2]
|
|
if (!target) {
|
|
console.error('dispatch.js: missing target (expected one of: dev, build, start)')
|
|
process.exit(2)
|
|
}
|
|
|
|
const studioRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..')
|
|
|
|
// Shell env wins, then `.env.local`, then `.env` — the same precedence
|
|
// scripts/serve.js and vite use, so STUDIO_FRAMEWORK set in either file is
|
|
// picked up (not just `.env.local`).
|
|
const fileEnv = readEnvFiles(studioRoot, ['.env', '.env.local'])
|
|
const studioFramework = process.env.STUDIO_FRAMEWORK ?? fileEnv.STUDIO_FRAMEWORK
|
|
const framework = studioFramework === 'tanstack' ? 'tanstack' : 'next'
|
|
const script = `${target}:${framework}`
|
|
|
|
// Use async `spawn` rather than `spawnSync` — long-running dev servers
|
|
// (vite dev / next dev) wedge under `spawnSync` because Node holds the
|
|
// event loop and stdin doesn't flow through cleanly. The dev server says
|
|
// "ready" then exits ~1s later. `spawn` + manual forwarding keeps the
|
|
// child interactive and lets the parent exit cleanly when the child does.
|
|
const child = spawn('pnpm', ['run', script], {
|
|
stdio: 'inherit',
|
|
env: process.env,
|
|
})
|
|
|
|
const forwardSignal = (signal) => {
|
|
if (!child.killed) child.kill(signal)
|
|
}
|
|
for (const signal of ['SIGINT', 'SIGTERM', 'SIGHUP', 'SIGQUIT']) {
|
|
process.on(signal, () => forwardSignal(signal))
|
|
}
|
|
|
|
child.on('exit', (code, signal) => {
|
|
if (signal) process.kill(process.pid, signal)
|
|
else process.exit(code ?? 1)
|
|
})
|
|
|
|
child.on('error', (err) => {
|
|
console.error('dispatch.js: failed to spawn child:', err)
|
|
process.exit(1)
|
|
})
|