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

@danielturner/lit-state

v1.0.1

Published

lit-state a lightweight state management solution

Downloads

22

Readme

<lit-state>

A lightweight state management with localstorage persistance.

Installation

#npm i @danielturner/lit-state

Usage

After adding lit-state to your application you need to replace LitElement with LitState for ANY view that is going to be using or managing state.

Example:

import { css, html } from 'lit-element';
import { LitState } from '../../lit-state/index.js';

export class TestState extends LitState {

Setting state in properties is your next step:

  static get properties() {
    return {
      state: {
        type: Object,
      },
    };
  }

Note: Your properties should have more properties than state

Set the initial value for state in the constructor, don't forget to set the keys you are interested in following for this view.

  constructor() {
    super();
    this.state = {
      welcome: '',
      counter: 0,
    };
  }

Note: Your constructor most likely will have more than just state.

One place in your app (possible the app's shell) will control the state. This element is the controller. Place it in your render method.

      <lit-controller></lit-controller>

To initialize a value outside the constructor use the firstUpdated method Calling the notify change triggers a state change across your app.

  firstUpdated() {
    this.notifyChange('welcome', 'Welcome to state');
  }

State changes can be anything, and any time during your apps lifecycle.

  __increment() {
    this.counter += 1;
    this.notifyChange('counter', this.counter);
  }

Or leverage the updated lifecycle.

  updated(changeProperties) {
    changedProperties.forEach((oldValue, propName) => {
      console.log(`${propName} changed. oldValue: ${oldValue}`);
      this.notifyChange(propName, this[propName]);
    });
  }

LitState uses two events stateChanged and stateChangeRequest

It is not recommended to use these to trigger updates.

Configuration

If you want to use sessionStorage instead of localStorage to limit the persistence to the session. Simply change the controller element in the render method to the following.

  <lit-controller sessionStorage>