cerealklr
cerealklr
SSolidJS
Created by cerealklr on 3/23/2024 in #support
How do you preserve reactivity across package boundaries?
that took a while even after knowing the problem, but eventually determined that peer dependencies and linked packages using vanilla npm is still problematic. The only real solution I found (outside of switching to one of the other package managers) was to npm link the parent project's solid-js package from the child module o.0 Regardless, everything's up and running now, thanks!
10 replies
SSolidJS
Created by cerealklr on 3/23/2024 in #support
How do you preserve reactivity across package boundaries?
I'll poke around in the library to see why it's still dragging a version of solid along and update when I figure it out (or if I need more help). Thanks for the great advice!
10 replies
SSolidJS
Created by cerealklr on 3/23/2024 in #support
How do you preserve reactivity across package boundaries?
Indeed that seems to be the problem!
10 replies
SSolidJS
Created by cerealklr on 3/23/2024 in #support
How do you preserve reactivity across package boundaries?
clever! I'll give that a shot, thanks
10 replies
SSolidJS
Created by cerealklr on 3/23/2024 in #support
How do you preserve reactivity across package boundaries?
1. Thanks, that could be a lead. The parent application is an obsidian plugin which runs in electron. It's maybe possible that's leading us down some SSR path I guess (?) 2. Interesting, I use vanilla npm for both and made solid a peer dependency I don't see any obvious printed warnings from solid about multiple versions in obsidian's dev console
10 replies