Paul Trowbridge
35f9b7b048
Two things the trace showed, one of them a wrong call on my part. getTable() was the wrong thing to wait on. The re-apply threw "No table set" two milliseconds after the event, meaning getTable() had already resolved while getView() still had not -- it is the view that is missing around a rebuild, not the table. There is no predicate for "the view is ready", so attempt applyDepth and retry until it stops throwing, up to 5s. And the shim matched nothing: not one callback reported a viewer. closest() stops at a shadow boundary, so it cannot climb from an element inside Perspective's shadow root out to the host, which is where the observed elements live. Walk host to host via getRootNode().host instead. The shim now also logs every callback it sees under [pf-obs], matched or not, with a description of each target. If it still reports nothing at all, the shim is not installed and the problem is import order rather than matching. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| vendor | ||
| .gitignore | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| vite.config.js | ||
React + 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 Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.