We could improve the individual event types such as click by adjusting it to

click(node: EventTarget, useCapture?: boolean): Stream<MouseEvent>;

This would avoid the need to do manual typecasting for users.

It may also be possible to improve the typings of domEvent with at least a change to

domEvent<T extends Event>(eventType: string, node: EventTarget, useCapture?: boolean): Stream<T>

but we may want to consider typing eventType with a union type of all of the standardized event types. I have an existing list of such types here.

Hi, I keep getting this warning along with an unmet peer depedency warning for [email protected] in my project, despite having the most recent releases of both installed.

I'm not sure what the problem is exactly, but I'm guessing the most@^0.19.0 is only good for up to the highest version of the same major version?

Should we update the @^version for most here or is there another way to get rid of this warning?

I noticed that the latest version at GitHub has not been published to npm, after getting this warning:

npm WARN @most/[email protected] requires a peer of most@^0.18.0 but none was installed.

Overview

Publish this library to NPM

Motivation

So we can all use it ;)

I’m trying to use dom-event with Chokidar, because it’s the closest thing I’ve found to fromEvent from Most v.1. But there are two problems with it:

1. Chokidar watcher doesn’t have addEventListener method, only addListener and on.
2. It feels kinda silly to use something called DOM event for events that have nothing to do with DOM.

I could live with the second one, but can we do something about the first? For instance, customize the method that adds a listener to a “node”? Or is it outside of dom-event’s scope and it’s better to just copy domEvent and create a separate fromEvent package?

Hi, are you up for publishing a new version to NPM so type definitions are included?

I am working more with TypeScript, and the @most/dom-event type defs are required for a successful build.

Thank you!