Chris Freeman

Update on this, it looks like there is an issue with how `@preact/signals-react` incorporates with the JSX runtime. You can circumvent this by updating vite react plugin to use the...

Update: this appears to only happen when using the automatic JSX runtime. If I instead use the classic runtime, the component behaves as expected. This might also be related to...

Good catch. Yes, you're correct. It only seems to come up when actually extends a tsconfig from another package.

Any chance this is related to a bigger problem? I have a generator I built for mobx and ran into the exact same this. Generated apps just fine a few...

@markerikson Hi there! Thanks for opening up the issue, this is a good find. I think I've found a fairly straightforward fix. > Any chance you could find a way...

Just published v0.0.12 containing these changes if you want to give them a shot. > Does that mean that when we end up reading the final result of whatever derived...

I'm super curious to hear more about your specific use case. If you find that this doesn't work and can come up with some kind of repro I'd love to...

Ah, this is really interesting. In all honesty, I don't think an actual Signalis store is the right fit here since it's really intended more as an abstraction over the...

This is great. I'm not at a computer right now, but looking at your code I'm guessing that the Signalis implementation just isn't memoizing anything (which seems to be confirmed...

@markerikson well, the bad news is i haven't *beaten* your benchmark, but I have gotten things a lot closer with some minor tweaks. Here's what I have so far: ```ts...