Files
supabase/pnpm-workspace.yaml
T
Kody JacksonandIvan Vasilov 6572fad288 fix(studio / ui) - update xss vuln version of tanstack (#51141)
## Problem

When I bumped the pnpm-lock file in an unrelated KB fix (#51132), I
believe that refreshed the build cache (either that, or Vercel started
flagging this issue very recently).

At any rate, builds are now failing b/c of a [vulnerable
Tanstack/react-start
package](https://github.com/TanStack/router/security/advisories/GHSA-qx66-fv34-fjm8),
which this PR attempts to fix.

```
The build blocks vulnerable @tanstack/react-start@1.168.18 due to an XSS security check.
```

<img width="1355" height="397" alt="image"
src="https://github.com/user-attachments/assets/7d0d90fb-009c-4a0b-aadc-b526e0fcce0a"
/>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Chores**
* Updated project maintenance settings and supporting TanStack package
versions.
* Improved error reporting so standard errors include their stack trace,
while other error values are logged directly.
  * No app features were added or removed.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
2026-10-02 00:42:12 +02:00

153 lines
4.7 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.8.0-rc.3
'@sentry/nextjs': ^10.59.0
'@sentry/tanstackstart-react': ^10.59.0
'@supabase/auth-js': 2.116.0
'@supabase/postgrest-js': 2.116.0
'@supabase/realtime-js': 2.116.0
'@supabase/ssr': 0.12.7
'@supabase/supabase-js': 2.116.0
'@tanstack/react-router': ^1.170.41
'@tanstack/react-start': ^1.168.60
'@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': ^5.0.0
'@vitest/ui': ^5.0.0
cn: ^0.4.0
lodash: ^4.18.1
lodash-es: ^4.18.1
monaco-editor: 0.52.2
next: ^16.3.5
next-themes: ^0.4.6
postcss: ^8.5.18
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
velite: ^0.4.0
vitest: ^5.0.0
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
msgpackr-extract: 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
- '@astrojs/markdown-satteri@0.3.8'
- astro@7.2.6
- next@16.3.5
- '@next/env@16.3.5'
- '@next/swc-darwin-arm64@16.3.5'
- '@next/swc-darwin-x64@16.3.5'
- '@next/swc-linux-arm64-gnu@16.3.5'
- '@next/swc-linux-arm64-musl@16.3.5'
- '@next/swc-linux-x64-gnu@16.3.5'
- '@next/swc-linux-x64-musl@16.3.5'
- '@next/swc-win32-arm64-msvc@16.3.5'
- '@next/swc-win32-x64-msvc@16.3.5'
- '@tanstack/react-router@1.170.41'
- '@tanstack/react-start-client@1.168.39'
- '@tanstack/react-start-rsc@0.1.59'
- '@tanstack/react-start-server@1.167.46'
- '@tanstack/react-start@1.168.60'
- '@tanstack/react-store@0.11.2'
- '@tanstack/router-core@1.171.34'
- '@tanstack/router-generator@1.167.40'
- '@tanstack/router-plugin@1.168.42'
- '@tanstack/start-client-core@1.170.34'
- '@tanstack/start-plugin-core@1.171.49'
- '@tanstack/start-server-core@1.169.39'
- '@tanstack/start-storage-context@1.167.36'
- '@tanstack/store@0.11.2'
overrides:
'@ardatan/relay-compiler>immutable': ^3.8.3
'monaco-editor': 'catalog:'
'@mapbox/node-pre-gyp>tar': ^7.5.21
'@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.21
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.21
nodemailer: ^7.0.11
postcss: 'catalog:'
qs: ^6.15.2
refractor>prismjs: ^1.30.0
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