Cross-origin (5173 vs 4000) blocked the auth cookie from reaching the bridge — every /database slash command request 401'd silently. Two changes: 1. vite.config.ts: add /bridge -> http://localhost:4000 proxy with path rewrite + /bridge-events -> /api/events for SSE. Same-origin = browser sends the auth cookie automatically. 2. bridge-client.ts: resolveBridgeUrl() defaults to /bridge instead of absolute http://localhost:4000. Also adds a VITE_BRIDGE_TOKEN env fallback for dev (the bridge requires Bearer auth and the Docmost session cookie is HttpOnly so JS cannot read it). Patch 021. |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .dockerignore | ||
| .gitignore | ||
| Dockerfile.e2e | ||
| eslint.config.mjs | ||
| index.html | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
| vitest.config.mts | ||
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
parserOptionsproperty like this:
parserOptions: {
ecmaVersion: 'latest',
sourceType: 'module',
project: ['./tsconfig.json', './tsconfig.node.json'],
tsconfigRootDir: __dirname,
},
- Replace
plugin:@typescript-eslint/recommendedtoplugin:@typescript-eslint/recommended-type-checkedorplugin:@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-runtimeto theextendslist