67057de214
Addresses the #147 review (Approve with comments): - Add footnote-views.structure.test.tsx: a structural regression guard asserting the editable NodeViewContent is the FIRST child of FootnotesListView and FootnoteDefinitionView, with no contenteditable=false chrome before it. The whole #146 fix rests on this DOM-order invariant; the macOS caret symptom needs a real browser, but the order proxy is testable in jsdom. Stubs @tiptap/react so the views render as plain DOM — the test passes on the fixed order and fails on the pre-fix chrome-first order. - Reword the code-block-view comment: it claimed a "top-right overlay (the transclusion pattern)", but the menu stays fully in flow as a full-width row lifted via flex `order: -1` (the .codeBlock wrapper is a flex column). No overlay/absolute positioning. 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