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
SolidJS Primitives to manage creating event listeners.
A set of primitives that help with listening to DOM and Custom Events.
makeEventListener
— Non-reactive primitive for adding event listeners that gets removed onCleanup.makeEventListenerStack
— Creates a stack of event listeners, that will be automatically disposed on cleanup.createEventListener
— Reactive version of makeEventListener
, that takes signal arguments to apply new listeners once changed.createEventSignal
— Like createEventListener
, but captured events are stored in a returned signal.createEventListenerMap
— A helpful primitive that listens to a map of events. Handle them by individual callbacks.WindowEventListener
— Listen to the window
DOM Events, using a component.DocumentEventListener
— Listen to the document
DOM Events, using a component.preventDefault
— Wraps event handler with e.preventDefault()
call.stopPropagation
— Wraps event handler with e.stopPropagation()
call.stopImmediatePropagation
— Wraps event handler with e.stopImmediatePropagation()
call.npm install @solid-primitives/event-listener
# or
yarn add @solid-primitives/event-listener
makeEventListener
@2.0.0
Can be used to listen to DOM or Custom Events on window, document, or any EventTarget.
Event listener is automatically removed on root cleanup. The clear() function is also returned for calling it early.
import { makeEventListener } from "@solid-primitives/event-listener";
const clear = makeEventListener(
document.getElementById("myButton"),
"mousemove",
e => console.log("x:", e.pageX, "y:", e.pageY),
{ passive: true }
);
// to clear all of the event listeners
clear();
// when listening to element refs, call it inside onMount
let ref!: HTMLDivElement
onMount(() => {
makeEventListener(ref, "click", e => {...}, { passive: true });
});
<div ref={ref} />;
// you can provide your own event map type as well:
// fill both type generics for the best type support
makeEventListener<{ myCustomEvent: MyEvent; other: Event }, "myCustomEvent">(
window,
"myCustomEvent",
() => console.log("yup!")
);
// just don't use interfaces as EventMaps! (write them using `type` keyword)
makeEventListenerStack
@2.0.0
Creates a stack of event listeners, that will be automatically disposed on cleanup.
import { makeEventListenerStack } from "@solid-primitives/event-listener";
const [listen, clear] = makeEventListenerStack(target, { passive: true });
listen("mousemove", handleMouse);
listen("dragover", handleMouse);
// remove listener (will also happen on cleanup)
clear();
createEventListener
Reactive version of makeEventListener
, that can take signal target
and type
arguments to apply new listeners once changed.
import { createEventListener } from "@solid-primitives/event-listener";
createEventListener(
document.getElementById("myButton"),
"mousemove",
e => console.log("x:", e.pageX, "y:", e.pageY),
{ passive: true }
);
// target element and event name can be reactive signals
const [ref, setRef] = createSignal<HTMLElement>();
const [type, setType] = createSignal("mousemove");
createEventListener(ref, type, e => {...});
// when using ref as a target, pass it in a function – function will be executed after mount
// or wrap the whole primitive in onMount
let ref;
createEventListener(() => ref, "mousemove", e => {});
<div ref={ref} />;
// 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)
Since version @2.0.0
createEventListener
and other reactive primitives aren't returning a clear()
function, because of it's flawed behavior described in this issue.
Although there are still ways to remove attached event listeners:
target
or type
arguments to an empty array.const [type, setType] = createSignal<"click" | []>("click");
createEventListener(window, type, e => {...});
// remove listener:
setType([]);
createEventListener
primitive in Solid's createRoot
or createBranch
| createDisposable
from "@solid-primitives/rootless".import { createDisposable } from "@solid-primitives/rootless";
const clear = createDisposable(() => createEventListener(element, "click", e => {...}));
// remove listener:
clear();
@1.4.3
You can listen to multiple events with single createEventListener
primitive.
createEventListener(el, ["mousemove", "mouseenter", "mouseleave"], e => {});
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>;
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 = createEventSignal(el, "mousemove", { passive: true });
createEffect(() => {
console.log(lastEvent()?.x, lastEvent()?.y);
});
createEventListenerMap
A helpful primitive that listens to a map of events. Handle them by individual callbacks.
import { createEventListenerMap } from "@solid-primitives/event-listener";
createEventListenerMap(element, {
mousemove: mouseHandler,
mouseenter: e => {},
touchend: touchHandler
});
// both target can be reactive:
const [target, setTarget] = createSignal(document.getElementById("abc"));
createEventListenerMap(
target,
{
mousemove: e => {},
touchstart: e => {}
},
{ passive: true }
);
// 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 => {}
});
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)} />;
preventDefault
Wraps event handler with e.preventDefault()
call.
import { preventDefault, makeEventListener } from "@solid-primitives/event-listener";
const handleClick = e => {
concole.log("Click!", e);
};
makeEventListener(window, "click", preventDefault(handleClick), true);
// or in jsx:
<div onClick={preventDefault(handleClick)} />;
stopPropagation
Wraps event handler with e.stopPropagation()
call.
import { stopPropagation, makeEventListener } from "@solid-primitives/event-listener";
const handleClick = e => {
concole.log("Click!", e);
};
makeEventListener(window, "click", stopPropagation(handleClick), true);
// or in jsx:
<div onClick={stopPropagation(handleClick)} />;
stopImmediatePropagation
Wraps event handler with e.stopImmediatePropagation()
call.
import { stopImmediatePropagation, makeEventListener } from "@solid-primitives/event-listener";
const handleClick = e => {
concole.log("Click!", e);
};
makeEventListener(window, "click", stopImmediatePropagation(handleClick), true);
// or in jsx:
<div onClick={stopImmediatePropagation(handleClick)} />;
You may view a working example here: https://codesandbox.io/s/solid-primitives-event-listener-elti5
See CHANGELOG.md
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.