Files
supabase/apps/studio/hooks/use-check-latest-deploy.tsx
9eab4f8fbf build(studio): Vite/TanStack-Start build pipeline behind flag (stack 1/6, from #46424) (#47107)
**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 <10985857+alaister@users.noreply.github.com>
Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
2026-06-24 17:55:22 +08:00

104 lines
3.4 KiB
TypeScript

import { IS_PLATFORM } from 'common'
import dayjs from 'dayjs'
import { useRouter } from 'next/router'
import { useEffect, useRef, useState } from 'react'
import { toast } from 'sonner'
import { Button, StatusIcon } from 'ui'
import { useDeploymentCommitQuery } from '@/data/utils/deployment-commit-query'
import { BASE_PATH } from '@/lib/constants'
const DeployCheckToast = ({ id }: { id: string | number }) => {
const router = useRouter()
return (
<div className="flex gap-3 flex-col w-full">
<div className="flex gap-3 flex-row">
<StatusIcon variant="default" className="mt-0.5" />
<div className="flex w-full justify-between flex-col text-sm">
<p className="text-foreground">A new version of this page is available</p>
<p className="text-foreground-light">Refresh to see the latest changes.</p>
</div>
</div>
<div className="flex gap-5 justify-end">
<Button variant="outline" onClick={() => toast.dismiss(id)}>
Not now
</Button>
<Button
onClick={() => {
// Clear the deployment pin so the reload lands on the latest
// version. No-op on Next (the cookie isn't set there).
document.cookie = `__vdpl=; Path=${BASE_PATH || '/'}; Max-Age=0`
router.reload()
}}
>
Refresh
</Button>
</div>
</div>
)
}
// This hook checks if the user is using old Studio pages and shows a toast to refresh the page. It's only triggered if
// there's a new version of Studio is available, and the user has been on the old dashboard (based on commit) for more than 24 hours.
// [Joshen] K-Dog has a suggestion here to bring down the time period here by checking commits
export function useCheckLatestDeploy() {
const [currentCommitTime, setCurrentCommitTime] = useState('')
const [isToastShown, setIsToastShown] = useState(false)
const { data: commit } = useDeploymentCommitQuery({
enabled: IS_PLATFORM,
staleTime: 1000 * 60 * 10, // 10 minutes
})
const commitLoggedRef = useRef(false)
useEffect(() => {
if (commit && !commitLoggedRef.current) {
const commitTime =
commit.commitTime === 'unknown'
? 'unknown time'
: dayjs(commit.commitTime).format('YYYY-MM-DD HH:mm:ss Z')
console.log(
`Supabase Studio is running commit ${commit.commitSha} deployed at ${commitTime}.`
)
commitLoggedRef.current = true
}
}, [commit])
useEffect(() => {
if (!commit || commit.commitTime === 'unknown') {
return
}
// set the current commit on first load
if (!currentCommitTime) {
setCurrentCommitTime(commit.commitTime)
return
}
// if the current commit is the same as the fetched commit, do nothing
if (currentCommitTime === commit.commitTime) {
return
}
// prevent showing the toast again if user has already seen and dismissed it
if (isToastShown) {
return
}
// check if the time difference between commits is more than 24 hours
const hourDiff = dayjs(commit.commitTime).diff(dayjs(currentCommitTime), 'hour')
if (hourDiff < 24) {
return
}
// show the toast
toast.custom((id) => <DeployCheckToast id={id} />, {
duration: Infinity,
position: 'bottom-right',
})
setIsToastShown(true)
}, [commit, isToastShown, currentCommitTime])
}