Svelte supports rxjs observables but it is not reflected in types

[olehmisar]

Describe the bug

I cannot use an rxjs.Observable with derived because svelte's Unsubscriber is not typed properly:

svelte/src/runtime/store/index.ts

Lines 6 to 7 in 3bc791b

	/** Unsubscribes from value updates. */
	export type Unsubscriber = () => void;

It should be typed as

export type Unsubscriber = { unsubscribe(): void; } | (() => void);

Reproduction

import { of } from 'rxjs'
const value = of(0);
derived(value, value => value + 2) // type error

Logs

No response

System Info

not relevant

Severity

annoyance

[dummdidumm]

This is an implementation detail for rxjs interop, but I'm not sure we want to expose it publicly. If you have a rxjs observable, why would you want to use it with derived anyway? Can't use you .pipe and the rxjs operators for that?

[olehmisar]

I want to mix svelte stores with rx observables

[hackape]

Your request is legit, however the severity is so over-stated. I can easily fix it with @ts-ignore and move on. Please report severity properly.

[samal-rasmussen]

I've taken to using these two helpers in order to get interop:

export function store_to_observable<T>(store: Writable<T> | Readable<T>): Observable<T> {
	return new Observable<T>((observer) => {
		return store.subscribe((value) => observer.next(value));
	});
}

export function observable_to_store<T>(observable: Observable<T>): Readable<T> {
	const store = Readable<T>();
	observable.subscribe((value) => store.set(value));
	return store;
}

But it sound to me like doing this is perfectly safe:

export function observable_to_store<T>(observable: Observable<T>): Readable<T> {
	return observable as any as Readable<T>;
}

Is this correct?

[L2Eme]

observable as unknown as Readable<T>;

It's useful anyway