Kieran Molloy

Hey, I think I found the problem, ServiceParams extends AdapterParams, which looks like { adapter?: A; paginate?: PaginationParams; } Where type PaginationParams = false | PaginationOptions; Therefore using { paginate:...

+1 on this. If you use the plugin in an environment that supports hot reloading each reload adds a new set of listeners. Not a major issue, but it would...

This is still broken. Here's a simpler version of the temporary workaround that seems to work ok. Essentially, what is does is watch the channel for a "Access token has...

> @create-signal are you seeing this with supabase-js? if so which version? > > I also think there's some element on supabase-js where we're not properly setting the token back...

Just FYI, i think the `push realtime:db-changes-test access_token (387) {access_token: 'OLD_TOKEN'}` message in that log was a red herring and is completely unrelated It looks like the backend server sends...

We kept seeing this error reported in our logs after updating to timer v1.4.3. I eventually wrote our own helpers that use `createTimer` directly and that seems ok. ``` function...

Nope! The type errors can be suppressed with @ts-expect-error and the library works as expected. Perhaps I turn this PR into an Issue instead to make it more easily searchable...