enteleform
Explore posts from serversBroken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
i did just run into something when trying to implement your Iconify wrapper though. it worked fine when it was in the source code of the Obsidian extension where I'm running into the issue. then I tried moving it to an external module so that I can use it across all of my projects, and the same issue started occurring as with
@iconify-icon/solid
.
that at least narrows it down to something to do with module-sourced components and/or the build process of said modules or the extension itself...39 replies
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
could be tough to assemble a 1:1 repro, kinda have like a personal framework of modules that are all contributing a bit to the final output. might take a shot at it when I get a chance.
39 replies
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
yeh I guess I'll include that as a lib wrapper in my app, thanks for your help with the workarounds!
kinda bugs me that I couldn't track down the root of the issue though... just ran
safe-stringify
on my final vite config (it's built dynamically with a few modules I have for Vite, Solid, Obsidian, etc.) and don't see any glaring issues.39 replies
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
that does work, although it also results in flashing every time something in the dependency chain updates rather than only when the final value is changed. e.g. on every timer tick.
39 replies
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
my current dev workflow is to just manually run a full build whenever I'm ready to test some changes, haven't been using a build-watch setup.
i ended up finding that
{dev:true}
resolved the issue either through trial and error or might have seen a recommendation about it while researching the issue. before that, I didn't have that option in my config at all.39 replies
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
39 replies
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
Thanks for the demo. I just replicated it and can confirm that a barebones extension implementation works as expected. However, running the exact same code in my actual extension does not work. Seems like I might have to debug my Vite config... can't think of what sort of thing might cause that issue off the top of my head though 🤔.
39 replies
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
It works fine in the StackBlitz example though, so I'm not sure what aspects of [Obsidian, Solid, Vite, Iconify, etc.] are playing into the issue in the actual production environment.
39 replies