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-shared-state-test

v0.0.2

Published

Shared state management for LitElement

Downloads

2

Readme

Lit Shared State

The easiest way to share global state between LitElement instances

Note: requires [email protected]

Highlights

lit-shared state was built to be..

  • ..reactive - state that can be shared across
  • ..simple - extremely minimal api surface, not much doc required :)
  • ..performant - lazy: only relevant slices of state lead to updates
  • ..flexible - state storage can be customized (for instance to use localstorage etc..)
  • ..tiny - less than 150 lines of commented typescript (~1KB minified), no dependencies (except for lit)

Installation

npm install lit-shared-state

Usage

import { LitElement, html } from "lit";
// this is all you need
import { state } from "lit-shared-state";

class State {
  // one line to declare anything as state
  // any subsequent change will redraw
  // all components that depend on it
  @state reactiveState: number = 1;
  // ..
}
const globalState = new State();

class CompA extends LitElement {
  // one line to pull in a slice of state
  @state state = globalState;

  render() {
    return html`<button @click=${() => this.state.reactiveState++}>
        ${this.state.reactiveState}
    </button>`;
  }
}

class CompB extends LitElement {
  // use state in multiple components
  @state state = globalState;

  render() {
    return html`<div> I am in sync:
        ${this.state.reactiveState}
    </div>`;
  }
}

// manipulating state from anywhere wills
// lead to update for all LitElements that depend on it
globalState.reactiveState += 41;

Gotchas

Updating nested objects

Updating nested fields in @state-annotated properties will not trigger a rerender (behavior is the same as in LitElement).

class State {
  @state object: { a: 'a', b: 'b' };
  @state array: ['a', 'b'];
}
const myState = new State();

// these will not trigger updates:
myState.object.c = 'c';
myState.array.push('c');

// instead use explicit assignment (+ spread operators) like this:
myState.object = { ...myState.object, c: 'c' };
myState.array = [ ...myState.object, 'c' ];

How does it compare

lit-element-state

This project is heavily inspired by https://github.com/gitaarik/lit-state. And has a very similar feature set and scope. The main difference is that we ..

  • .. provide typescript implementation
  • .. rely a less intrusive lit 2.x ReactiveController pattern
  • .. provide unit-tested code with 100% coverage