The read-only embed renderer mounts a Tiptap EditorProvider with the looked-up content, but Tiptap consumes the `content` option only at initial mount. After Refresh busted the lookup cache and re-fetched fresh content, the new content prop never reached the sub-editor, so the embed appeared not to update at all. Key PageEmbedContent on result.sourceUpdatedAt (the source page's updatedAt, already returned by the lookup and bumped on every persisted content change) so the component and its EditorProvider remount and apply the refreshed content when the source changes. Note: server-side freshness vs. live collab edits is bounded by the 10s persist debounce (collaboration.gateway.ts) — that separate limitation stays documented in #40 and is out of scope here; this commit fixes the client never re-rendering. 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