mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
Alaister YoungandAlaister Young
8d4d3b57e0
Makes the self-hosted Docker image buildable with the TanStack/Vite
build alongside the existing Next one. The Dockerfile's new
`STUDIO_FRAMEWORK` build arg (default: `next`) selects which framework
lands in the image — the same variable `scripts/dispatch.js` keys on
everywhere else, so `--build-arg STUDIO_FRAMEWORK=tanstack` is the
docker spelling of the existing switch. Both flavors assemble a
normalized `/srv` tree, so a single production stage serves either with
the same CMD (`node apps/studio/server.js`), port 3000, and healthcheck.
Unlike Next's self-contained standalone output, the Vite SSR bundle
externalizes studio's dependencies and resolves them from `node_modules`
at request time, so the tanstack runtime tree is a prod-only `pnpm
deploy` plus the built `dist/`. The boot smoke test runs a second time
against that pruned tree, so a runtime import that's missing from
`dependencies` fails the image build instead of 500ing the deployed
container — which is exactly how this PR caught four packages
misclassified as devDependencies (`braintrust` +
`@smithy/property-provider` via the AI routes, `libpg-query` via the
parse-query API route, `@radix-ui/react-use-escape-keydown` via the
Queues panel; split into its own commit).
**Changed:**
- `apps/studio/Dockerfile`: `ARG STUDIO_FRAMEWORK` selects `build-next`
/ `build-tanstack` stages via `FROM build-${STUDIO_FRAMEWORK}`; both
normalize into one production layout
- `apps/studio/package.json`: moved the four runtime-imported packages
from devDependencies to dependencies (versions unchanged)
- `apps/studio/vite.config.ts`: pinned `preview.host` to `127.0.0.1` —
the prerender step boots `vite preview` and crawls its resolved URL, and
the default `localhost` host lets the server bind the IPv6 loopback
while the crawler fetches `127.0.0.1`, which ECONNREFUSEDs the whole
build inside BuildKit containers
- `.github/workflows/studio-docker-build.yml`: builds the tanstack image
as a second step (reuses the first build's layer cache; job name
unchanged)
**Added:**
- `build:studio:docker:tanstack` root script
Note: the tanstack image is ~2.0GB vs ~1.2GB for Next (externalized
`node_modules`); shrinking it via file tracing is a follow-up. Nothing
self-hosters pull changes until a tanstack-built image is published —
this makes it buildable and CI-checked.
## To test
- `pnpm build:studio:docker` then run the image against a stack —
behavior unchanged (healthcheck `/api/platform/profile` 200, `/` 307s to
`/project/default`)
- `pnpm build:studio:docker:tanstack` then run that image with the same
env — same healthcheck, redirect, and data endpoints (projects, pg-meta)
respond 200; browser loads Project Overview / Table Editor with no
requests leaving the container
- Both verified locally against the CLI stack (`host.docker.internal`
env, container reports `healthy`)
- Vercel + e2e checks on this PR exercise the `preview.host` change on
their runners
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Added TanStack-based Studio build support with a framework-selectable
Docker image.
- Added a local build command for the TanStack Studio Docker image.
- **Build & Deployment**
- Updated the Studio Docker build workflow to also publish a
TanStack-tagged Studio image when relevant.
- **Bug Fixes**
- Improved `vite preview` behavior in containers by binding to IPv4
loopback.
- Standardized the Studio container runtime port to `3000`.
- **Chores**
- Updated Studio runtime packages to support the TanStack build.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Alaister Young <10985857+alaister@users.noreply.github.com>
126 lines
3.8 KiB
YAML
126 lines
3.8 KiB
YAML
packages:
|
|
- apps/*
|
|
- packages/*
|
|
- blocks/*
|
|
- e2e/*
|
|
|
|
blockExoticSubdeps: true
|
|
engineStrict: true
|
|
updateNotifier: false
|
|
# Doesn't work because of Typescript issues with peer dependencies, see https://github.com/pnpm/pnpm/issues/9739
|
|
enableGlobalVirtualStore: false
|
|
|
|
catalog:
|
|
'@monaco-editor/react': ^4.7.0
|
|
'@sentry/nextjs': ^10.59.0
|
|
'@sentry/tanstackstart-react': ^10.59.0
|
|
'@supabase/auth-js': 2.110.8
|
|
'@supabase/postgrest-js': 2.110.8
|
|
'@supabase/realtime-js': 2.110.8
|
|
'@supabase/ssr': 0.10.2
|
|
'@supabase/supabase-js': 2.110.8
|
|
'@tanstack/react-router': ^1.169.2
|
|
'@tanstack/react-start': ^1.167.65
|
|
'@tanstack/react-table': ^8.21.3
|
|
'@types/node': ^22.0.0
|
|
'@types/react': ^19.2.14
|
|
'@types/react-dom': ^19.2.3
|
|
# TypeScript 7 has no programmatic API until 7.1, so `typescript` stays aliased
|
|
# to the 6.0-API compat package for tools that import it (typescript-eslint,
|
|
# Next.js build typechecking), while `@typescript/native` provides the native
|
|
# TS 7 `tsc` binary used by typecheck scripts.
|
|
# https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/
|
|
'@typescript/native': npm:typescript@~7.0.2
|
|
'@vitejs/plugin-react': ^6.0.1
|
|
'@vitest/coverage-v8': ^4.1.4
|
|
'@vitest/ui': ^4.1.4
|
|
lodash: ^4.18.1
|
|
lodash-es: ^4.18.1
|
|
monaco-editor: 0.52.2
|
|
next: 16.2.6
|
|
next-themes: ^0.4.6
|
|
postcss: ^8.5.10
|
|
radix-ui: ^1.4.3
|
|
react: ^19.2.6
|
|
react-dom: ^19.2.6
|
|
recharts: ^2.15.4
|
|
tailwindcss: ^4.2.4
|
|
tsx: ^4.22.0
|
|
typescript: ~6.0.2
|
|
valtio: ^2.3.2
|
|
vite: ^8.0.16
|
|
vite-tsconfig-paths: ^6.1.1
|
|
vitest: ^4.1.4
|
|
zod: 3.25.76
|
|
|
|
allowBuilds:
|
|
'@parcel/watcher': false
|
|
'@sentry/cli': false
|
|
'@supabase/build-icons@file:packages/build-icons': set this to true or false
|
|
'@supabase/pg-meta@file:packages/pg-meta': set this to true or false
|
|
ai-commands@file:packages/ai-commands: set this to true or false
|
|
api-types@file:packages/api-types: set this to true or false
|
|
common@file:packages/common: set this to true or false
|
|
config@file:packages/config: set this to true or false
|
|
contentlayer2: false
|
|
core-js: false
|
|
dev-tools@file:packages/dev-tools: set this to true or false
|
|
es5-ext: false
|
|
esbuild: false
|
|
icons@file:packages/icons: set this to true or false
|
|
libpg-query: false
|
|
msw: false
|
|
node-pty: true
|
|
protobufjs: false
|
|
shared-data@file:packages/shared-data: set this to true or false
|
|
sharp: false
|
|
supabase: true
|
|
ui-patterns@file:packages/ui-patterns: set this to true or false
|
|
ui@file:packages/ui: set this to true or false
|
|
|
|
minimumReleaseAge: 4320
|
|
|
|
minimumReleaseAgeExclude:
|
|
- '@ai-sdk/*'
|
|
- '@supabase/*'
|
|
- '@supabase-labs/*'
|
|
- typescript
|
|
- '@typescript/*'
|
|
# First-party, published from supabase-community/mdast-jsx.
|
|
- mdast-jsx
|
|
# The following are excluded to fix vulnerablities.
|
|
- react-use
|
|
|
|
overrides:
|
|
'@ardatan/relay-compiler>immutable': ^3.8.3
|
|
'monaco-editor': 'catalog:'
|
|
'@mapbox/node-pre-gyp>tar': ^7.5.19
|
|
'@sentry/webpack-plugin>uuid': ^11.1.1
|
|
'@usercentrics/cmp-browser-sdk>uuid': ^11.1.1
|
|
braintrust>esbuild: ^0.28.1
|
|
braintrust>uuid: ^11.1.1
|
|
cacache>tar: ^7.5.19
|
|
dompurify: ^3.3.2
|
|
express-rate-limit>ip-address: ^10.1.1
|
|
# Pin h3 v1 to a single version so the Nuxt registry example (vue-blocks)
|
|
# doesn't end up with two copies (1.15.10 + 1.15.11) and hit nominal
|
|
# H3Event type mismatches. v2 (h3@2) is intentionally left untouched.
|
|
'h3@1': 1.15.11
|
|
lodash: 'catalog:'
|
|
lodash-es: 'catalog:'
|
|
mdx-bundler>uuid: ^11.1.1
|
|
node-gyp>tar: ^7.5.19
|
|
nodemailer: ^7.0.11
|
|
postcss: 'catalog:'
|
|
qs: ^6.15.2
|
|
refractor>prismjs: ^1.30.0
|
|
supabase>tar: ^7.5.19
|
|
tmp: ^0.2.7
|
|
vite>esbuild: ^0.28.1
|
|
webpack: ^5.104.1
|
|
'codemirror-graphql>@codemirror/language': 6.11.0
|
|
'@esbuild-plugins/node-resolve>esbuild': ^0.28.1
|
|
|
|
patchedDependencies:
|
|
react-data-grid: patches/react-data-grid.patch
|