Ben Lesh

On Chrome, it's as simple as going to the Application tab in dev tools and clearing local data. Just make sure you have "uninstall service worker" checked.

I filed an issue upstream... because I agree it's confusing, but I'm not sure this is on us... https://github.com/microsoft/TypeScript/issues/56741 We might have a `pipe()` overload with zero arguments that we...

This a cool idea. @niklas-wortmann or @jakovljevic-mladen can you please have a look?

Rethinking this change. As most people will be using a deep equals algorithm that is less forgiving with notifications structures. (i.e. matching `{ kind: 'N', value: 1 }` with `{...

No, we just need to publish 7.x again with the change. It's low-priority, but fixable with a publish.

Hi, @yuri-apanasik, thank you for your contribution. Please add a test and confirm that the test is broken in master _prior_ to changing any code.

> I know people would probably hate it, but have you considered a function that returns a function that would pipe the operator arguments and call the result with the...

> Why not call it pipe? @timdp Because it's not really just a `pipe`. It's applying `from` to the first argument. Technically it's `pipe(source, from, map(fn), ...)`

CORE TEAM: + The name needs to be bikeshedded + why not just direct people to use `pipe(from(x), ...operators)`? + maybe have `pipe(first, ...operators)` check the type of `first` and...

Personally, I still like `rx(source, ...operators)`. 1. It's terse. 2. It can replace `from(source)` in the long term with just `rx(source)`. (and `from` is sort of a bad name we...