Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
@solid-primitives/event-listener
Advanced tools
A set of primitives that help with listening to DOM and Custom Events.
createEventListener
- Very basic and straightforward primitive that handles multiple elements according to a single event binding.createEventSignal
- Like createEventListener
, but events are handled with the returned signal, instead of with a callback.createEventListenerMap
- A helpful primitive that listens to a map of events. Handle them by individual callbacks.createEventStore
- Similar to createEventListenerMap
, but provides a reactive store with the latest captured events.WindowEventListener
- Listen to the window
DOM Events, using a component.DocumentEventListener
- The same as WindowEventListener
, but listens to document
events.npm install @solid-primitives/event-listener
# or
yarn add @solid-primitives/event-listener
createEventListener
Can be used to listen to DOM or Custom Events on window, document, list of HTML elements or any EventTarget. The target prop can be reactive.
import { createEventListener } from "@solid-primitives/event-listener";
const clear = createEventListener(
document.getElementById("myButton"),
"mousemove",
e => console.log("x:", e.pageX, "y:", e.pageY),
{ passive: true }
);
// to clear all of the event listeners
clear();
// target element, event name and options can be reactive signals
const [ref, setRef] = createSignal<HTMLElement>();
const [name, setName] = createSignal("mousemove");
const [options, setOptions] = createSignal({ passive: true });
createEventListener(ref, name, e => {}, options);
// you can provide your own event map type as well:
// fill both type generics for the best type support
createEventListener<{ myCustomEvent: MyEvent; other: Event }, "myCustomEvent">(
window,
"myCustomEvent",
() => console.log("yup!")
);
// just don't use interfaces as EventMaps! (write them using `type` keyword)
props passed to the directive are also reactive, so you can change handlers on the fly.
import { eventListener } from "@solid-primitives/event-listener";
// avoids tree-shaking the directive:
eventListener;
<button use:eventListener={["click", () => console.log("Click")]}>Click!</button>;
function createEventListener<
EventMap extends Record<string, Event>,
EventName extends keyof EventMap
>(
target: MaybeAccessor<Many<EventTarget>>,
eventName: MaybeAccessor<EventName>,
handler: (event: EventMap[EventName]) => void,
options?: MaybeAccessor<boolean | AddEventListenerOptions>
): ClearListeners;
// Directive
function eventListener(
target: Element,
props: Accessor<EventListenerDirectiveProps>
): EventListenerReturn;
type EventListenerDirectiveProps = [
name: string,
handler: (e: any) => void,
options?: AddEventListenerOptions | boolean
];
createEventSignal
Like createEventListener
, but events are handled with the returned signal, instead of with a callback.
import { createEventSignal } from "@solid-primitives/event-listener";
// all arguments can be reactive signals
const [lastEvent, clear] = createEventSignal(el, "mousemove", { passive: true });
createEffect(() => {
console.log(lastEvent()?.x, lastEvent()?.y);
});
// to clear all the event listeners
clear();
function createEventSignal<
EventMap extends Record<string, Event>,
EventName extends keyof EventMap = keyof EventMap
>(
target: MaybeAccessor<Many<EventTarget>>,
eventName: MaybeAccessor<EventName>,
options?: MaybeAccessor<boolean | AddEventListenerOptions>
): EventListenerSignalReturns<EventMap[EventName]>;
type EventListenerSignalReturns<Event> = [
lastEvent: Accessor<Event | undefined>,
clear: ClearListeners
];
createEventListenerMap
A helpful primitive that listens to a map of events. Handle them by individual callbacks.
import { createEventListenerMap } from "@solid-primitives/event-listener";
const clear = createEventListenerMap(element, {
mousemove: mouseHandler,
mouseenter: e => {},
touchend: touchHandler
});
// to clear all the event listeners
clear();
// both target and options args can be reactive:
const [target, setTarget] = createSignal(document.getElementById("abc"));
const [options, setOptions] = createSignal({ passive: true });
createEventListenerMap(
target,
{
mousemove: e => {},
touchstart: e => {}
},
options
);
// createEventListenerMap can be used to listen to custom events
// fill both type generics for the best type support
createEventListenerMap<
{
myEvent: MyEvent;
custom: Event;
other: Event;
},
"myEvent" | "custom"
>(target, {
myEvent: e => {},
custom: e => {}
});
import { eventListenerMap } from "@solid-primitives/event-listener";
// prevent tree-shaking:
eventListenerMap;
<div
use:eventListenerMap={{
mousemove: e => {},
click: clickHandler,
touchstart: () => {},
myCustomEvent: e => {}
}}
></div>;
function createEventListenerMap<
EventMap extends Record<string, Event>,
UsedEvents extends keyof EventMap = keyof EventMap
>(
target: MaybeAccessor<Many<EventTarget>>,
handlersMap: EventHandlersMap,
options?: MaybeAccessor<boolean | AddEventListenerOptions>
): ClearListeners;
createEventStore
Similar to createEventListenerMap
, but provides a reactive store with the latest captured events.
const [lastEvents, clear] = createEventStore(el, "mousemove", "touchend", "click");
createEffect(() => {
console.log(lastEvents?.mousemove.x);
});
// to clear all the event listeners
clear()
// both target and options args can be reactive:
const [target, setTarget] = createSignal(document.getElementById("abc"));
const [options, setOptions] = createSignal({ passive: true });
const [lastEvents] = createEventStore(target, options, "mousemove", "touchmove");
// createEventStore can be used to listen to custom events
// fill both type generics for the best type support
const [lastEvents] = createEventStore<
{
myEvent: MyEvent;
custom: Event;
unused: Event;
},
"myEvent" | "custom"
>(target, "myEvent", "custom");
// DON'T DO THIS:
const [{ mousemove }] = createEventStore(target, "mousemove", ...);
// the store cannot be destructured
function createEventStore<
EventMap extends Record<string, Event>,
UsedEvents extends keyof EventMap = keyof EventMap
>(
target: MaybeAccessor<Many<EventTarget>>,
...eventNames: UsedEvents[]
): EventListnenerStoreReturns<Pick<EventMap, UsedEvents>>;
// with options:
function createEventStore<
EventMap extends Record<string, Event>,
UsedEvents extends keyof EventMap = keyof EventMap
>(
target: MaybeAccessor<Many<EventTarget>>,
options: MaybeAccessor<boolean | AddEventListenerOptions>,
...eventNames: UsedEvents[]
): EventListnenerStoreReturns<Pick<EventMap, UsedEvents>>;
type EventListnenerStoreReturns<E> = [lastEvents: Store<Partial<E>>, clear: ClearListeners];
WindowEventListener
Listen to the window
DOM Events, using a component.
You can use it with any Solid's Control-Flow components, e.g. <Show/>
or <Switch/>
.
The event handler prop is reactive, so you can use it with signals.
import { WindowEventListener } from "@solid-primitives/event-listener";
<WindowEventListener onMouseMove={e => console.log(e.x, e.y)} />;
DocumentEventListener
The same as WindowEventListener
, but listens to document
events.
import { DocumentEventListener } from "@solid-primitives/event-listener";
<DocumentEventListener onMouseMove={e => console.log(e.x, e.y)} />;
You may view a working example here: https://codesandbox.io/s/solid-primitives-event-listener-elti5
0.0.100
First ported commit from react-use-event-listener.
1.1.4
Released a version with type mostly cleaned up.
1.2.3
Switched to a more idiomatic pattern: Warning: incompatible with the previous version!
1.2.5
Added CJS build.
1.2.6
Migrated to new build process.
1.3.0
(minor breaking changes to type generics and returned functions) Primitive rewritten to provide better types and more solidlike (reactive) usage. Added a lot more primitives.
1.3.7
Published recent major updates to latest tag.
FAQs
SolidJS Primitives to manage creating event listeners.
The npm package @solid-primitives/event-listener receives a total of 18,461 weekly downloads. As such, @solid-primitives/event-listener popularity was classified as popular.
We found that @solid-primitives/event-listener demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.