Files
zeekayandHanzo Dev 546c40db16 The dashboard builds on Vite 8 and React 19
query-string 9 exports a single object, so the pagination hook reads stringify
off it, the way the return-to hook already does.

react-router 7 is one package. Every import names it, so the app and its tests
share one router instance and one context; react-router-dom and its v5 types
are gone.

Vite 8 resolves tsconfig paths on its own, so vite-tsconfig-paths is gone and
resolve.tsconfigPaths takes its place.

faency carries @types/react 18 as a dependency. A pnpm override holds the whole
tree at the React 19 types the app declares, so faency's components type as JSX
components again.

The rest is what React 19 and TypeScript 7 ask for: useRef takes an initial
value, the error fallback narrows the unknown it is handed, sha512's output is
narrowed once where it meets @noble/ed25519, and the test setup replaces fetch
through vi.stubGlobal.

pnpm build, pnpm tsc and pnpm test are green; eslint still waits on
typescript-eslint support for TypeScript 7.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 03:19:59 -07:00

29 lines
662 B
TypeScript

/// <reference types="vitest" />
/// <reference types="vite/client" />
import react from '@vitejs/plugin-react'
import { defineConfig, loadEnv } from 'vite'
export default ({ mode }: { mode: string }) => {
process.env = { ...process.env, ...loadEnv(mode, process.cwd()) }
return defineConfig({
resolve: { tsconfigPaths: true },
base: process.env.VITE_APP_BASE_URL || '',
plugins: [react()],
server: {
open: 'index.dev.html',
port: 3000,
},
build: {
emptyOutDir: true,
outDir: './static',
},
test: {
environment: 'jsdom',
globals: true,
setupFiles: './test/setup.ts',
},
})
}