npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

lit-signals-helpers

v2.0.1

Published

Set of helpers on top of @lit-labs/preact-signals

Downloads

1

Readme

lit-signals-helpers

Set of helpers on top of @lit-labs/preact-signals

Decorator

If you prefer a decorator over a mixin, you can use @signalable:

import {signalable, signal} from 'lit-signals-helpers';

const $username = signal('John Doe');

@customElement('my-element')
@signalable
class E extends LitElement {
	// Called every time $username changes.
	render() {
		return html`
			<p>Hello ${$username}</p>

			<button @click=${this.#signout}>signout</button>
		`;
	}

	#signout() {
		$username.value = 'anonymous';
	}
}

Note: when a signal value changes it will update all the views that depends on it as long as views use @signalable of course.

html tagged template

Unmodified html tagged template from the @lit-labs/preact-signals package. The advantage of this tag over the decorator is that when a signal changes it will only update the DOM part that depends on it and do not request a complete update from the Lit element.

import {html, signal} from 'lit-signals-helpers';

const $username = signal('John Doe');

@customElement('my-element')
class E extends LitElement {
	render() {
		return html`Hello <b>${$username}</b>`;
	}
}

When $username changes somewhere, <b> content is automatically updated with the new value.

Local storage support

If you would like to persist your signal values between page refreshes, you can use this module.

Here's an example:

import {lsignal} from 'lit-signals-helpers';

export const $userName = lsignal('userstore', 'name', 'anonymous');
export const $useAge = lsignal('userstore', 'age', 0);

or using compound syntax

import {compound} from 'lit-signals-helpers';

// Using compound syntax improves readability.

const c = compound('userstore');

export const $userName = c.signal('name', 'anonymous');
export const $userAge = c.signal('age', 0);

// You can access all the compound signals for debugging purpose.
console.log(c.signals);
// Though Intellisense is unaware of the following type
// you can access and use a signal directly from the compound.
c.signals.$userName.value = 'John Doe';

// Export for general use.
export const userCompound = c;