S
SolidJS•2mo ago
Tom

Reactivity stopped - advice for debugging?

My app uses ProseMirror. ProseMirror lets you embed little UI widgets in the document ("node views"). It works great with Solid. The node-views are not part of the normal Solid render tree so I wrap the UI code in a createRoot I've got a bug where in a certain situation a node-view UI becomes non-reactive. I've reduced it down to a simple createEffect(() => console.log(...)) so I think it's unrelated to any dom issues. I've also disabled any code that disposes the created root. I'm really stuck with how to debug this. Any advice? What can cause a root to become non-reactive? (the rest of the app is still reactive) Thanks
1 Reply
Tom
TomOP•2mo ago
Also worth mentioning - it's reacting to a global store, not local signals, and other parts of the UI remain reactive to the store. Thanks for responding - just figured out it's not a Solid issue at all 🙈
Want results from more Discord servers?
Add your server