Niklas

Thanks for the quick answer! interesting, is just started with a clean installed MacBook — we'll see 👀

> I didn't realize that the context was exported, so this is what I've done within my app: > > ```tsx > import { Portal, useMenuContext } from "@chakra-ui/react"; >...

One of the few reasons `jest-marbles` may be used over `jasmine-marbles` is that due to the output of `jasmine-marbles` it's nearly impossible to compare complex observables. Here a simple comparison:...

> .on('system', {}, payload => { > if (payload.extension === 'postgres_changes' && payload.status === 'ok') { > console.log('Do something crazy!'); > } > }) Thanks for the updates @chasers, sorry...

This implementation is working fine for me and handles both disconnects (due to network / or tab beeing in the background) and also handles the initial subscription. - Invalidates all...

FYI @n8sabes , I've managed to "fix" this by merging all my original entry points into a single one. But after this the qwik compiler is too heavy for my...

Hm, about one third of the components use a context hook and if I remember correctly they don't work in lite / inline components. I'll consider throwing away the feature...

Lite components seem to work fine. Just in dev mode (`vite --mode ssr`) no tree-shaking is happening, so on the first user interaction with one of the lite components all...

Alright, so the icon package now works with multiple entrypoints + only lite components – but the warning is now back that I'm using multiple entrypoints. Thanks for the suggestions...

> I'd like to add that it seems like the error is harmless in the case of the icons package, but it can lead to actual things not working, see...