History

Corentin 5f7bce9b02 fix(client): read VITE_BRIDGE_TOKEN via process.env (define block target) — Patch 023 The previous fix (Patch 021) read import.meta.env.VITE_BRIDGE_TOKEN, but Vite only auto-exposes VITE_* in import.meta.env when the .env lives in apps/client/. Our .env is at the monorepo root and is loaded via loadEnv() in vite.config.ts, then injected through the define block under the 'process.env' key. So the runtime variable lives at process.env.VITE_BRIDGE_TOKEN, not import.meta.env.VITE_BRIDGE_TOKEN. Without this, the bridge proxy received no Bearer header and returned 401 Unauthorized for every /database slash command request — exactly what Corentin reported. Patch 023.		2026-05-08 12:34:38 +02:00
..
public	fix(acadenice): include parent-child edges in graph + space-scope view — R4.6	2026-05-08 12:14:28 +02:00
src	fix(client): read VITE_BRIDGE_TOKEN via process.env (define block target) — Patch 023	2026-05-08 12:34:38 +02:00
.dockerignore	fixes	2024-06-07 17:29:34 +01:00
.gitignore
Dockerfile.e2e	test(e2e): add data-testid attributes for Playwright e2e (Patch 008 R3.1.e)	2026-05-08 00:37:39 +02:00
eslint.config.mjs	chore: fix linting (#544 )	2024-12-09 14:51:31 +00:00
index.html	feat(acadedoc): add AcadeDoc branding, Brevo SMTP preset, UI customization — R4.4	2026-05-08 11:36:38 +02:00
package.json	feat(acadenice): add timeline view (Gantt) for databases — R4.1	2026-05-08 11:27:11 +02:00
postcss.config.js
README.md
tsconfig.json
tsconfig.node.json
vite.config.ts	fix(client): bridge same-origin proxy via Vite + dev token fallback — Patch 021	2026-05-08 12:32:33 +02:00
vitest.config.mts	fix(acadenice): resolve test suite failures across R3 sub-blocks (Patch 017)	2026-05-08 10:36:19 +02:00

README.md

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

Configure the top-level parserOptions property like this:

   parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json'],
    tsconfigRootDir: __dirname,
   },

Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
Optionally add plugin:@typescript-eslint/stylistic-type-checked
Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list