Claude d9d2233960 fix: prevent extensions recreation by stabilizing suggestion config dependencies
The root cause of broken autocompletion was that suggestion configs were
being extracted via .find() outside useMemo, creating new object references
on every render. These unstable references were then used as dependencies
for the extensions useMemo, causing TipTap extensions to be recreated on
every single render. This destroyed the suggestion system's internal state
including popup visibility and search results.

Changes:
- Move .find() calls inside the extensions useMemo
- Replace individual config dependencies with stable 'suggestions' array
- Extensions now only recreate when suggestions actually change (rare)

This matches React best practices: avoid computing values outside useMemo
when those values are used as dependencies, as they create unstable
references that defeat memoization.

The issue was NOT with TipTap's async handling (my first fix was wrong),
but with React's dependency tracking and object reference stability.
2026-01-20 18:08:56 +00:00
2025-12-22 20:40:16 +00:00
2026-01-14 19:24:37 +01:00

Grimoire

A Nostr protocol explorer and developer tool with a tiling window manager interface.

Features

  • Tiling Windows - Each window is a Nostr "app" (profile viewer, event feed, NIP docs, etc.)
  • Command Palette - Unix-style commands via Cmd+K to open apps and navigate
  • Multi-workspace - Virtual desktops with independent layouts
  • Real-time - Reactive event subscriptions with automatic updates

Stack

React 19, TypeScript, Vite, TailwindCSS, Jotai, Dexie, Applesauce

Getting Started

npm install
npm run dev

Scripts

Command Description
npm run dev Start dev server
npm run build Build for production
npm test Run tests in watch mode
npm run lint Lint code
npm run format Format code

License

MIT

Description
No description provided
Readme MIT 14 MiB
Languages
TypeScript 98.9%
CSS 0.8%
JavaScript 0.3%