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

sparx

v1.0.3

Published

Very minimal state management lib based on react hooks

Downloads

19

Readme

sparx

Very minimal state management lib based on react hooks.

Guide

store.js

create a store and a hook by using sparx


// make a store , there could be multi store in on app or just on, your choice
import createSparkHooks from "sparx";
const {useSpark, sparkle, useSubscribeStoreChange_UNSTABLE, useStore} = createSparkHooks();
export { useSpark, sparkle };

state.js

create a state.js where your sparks live, component can import sparks from this module

// import the sparkle method from the store
import {sparkle} from 'store.js'

// use sparkle to make a spark
export const data_1 = sparkle({
  key: 'string key',
  value: {} // any data
})

component_1.js

create a component which consume the spark by using the useSpark hook which from the store

import {useSpark} from 'store.js'
import {data_1} from 'state.js'

const Comp1 = () => {
  // by call the useSpark hook, you can get the data from the spark, and a updater to update the spark
  // the same as useState
  const [data1, setData1] = useSpark(data_1);
  // ....
  // your render logic
}

component_2.js

create a component comsume the same spark as the previous compoent, notice that, each of these two component updating the data by calling setData1 will trigger both component update/rerender

// 
import {useSpark} from 'store.js'
import {data_1} from 'state.js'

const Comp1 = () => {
  const [data1, setData1] = useSpark(data_1);
  // ....
  // your render logic
}

todo

[] complete senarios [] support aync spark [] data serialize, unserilaize [] store initial state [] dynamic spark helper [] memorize [*] documentation