The onAuthenticationFailed handler is created once per page (effect keyed on pageId), so it closed over the initial collab token and decoded a STALE value after a refetch. Worse, jwtDecode(undefined) throws, so when the token had not loaded (or the request failed) the handler crashed before it could refetch and reconnect — leaving the editor stuck disconnected. Mirror the latest token into a ref the handler reads live, and guard the decode: a missing or malformed token is treated as 'needs refresh' so it refetches and reconnects instead of throwing. A valid, unexpired token still early-returns. Also remove two local useState sync flags (isLocalSynced/isRemoteSynced) that were set but never read — the header indicator consumes the Jotai atoms, and the hook's return values were never destructured by any caller. The setter wrappers now drive only the atoms. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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