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

r-reactive-store

v0.3.1

Published

A simple way to read, create, update and remove item in a reactive and synchronous collection.

Downloads

4

Readme

Reactive Store

A simple way to read, create, update and remove item in a reactive and synchronous collection.

Example

// Create a store handling a collection of Todo
const store = createStore<{ todos: Todo }>('todos')

// Create a todo
store.todos.create({ id: 'a', label: 'Lorem', done: false })

// Access todo (no reactive)
store.todos.get('a')
// => { id: 'a', label: 'Lorem', done: false }

// Access todo (reactive)
store.todos.get$('a').subscribe(logger)
// => logger: { id: 'a', label: 'Lorem', done: false }

// Update todo
store.todos.update('a', { label: 'Ipsum', done: true })
// => logger: { id: 'a', label: 'Ipsum', done: true }

// Patch todo
store.todos.patch('a', { label: 'Lorem' })
// => logger: { id: 'a', label: 'Lorem', done: true }

// Remove todo
store.todos.remove('a')
// => logger: null

// Access list of todo's id (reactive)
store.todos.getAllIds$().subscribe(loggerBis)
// => loggerBis: []

// Create another todo
store.todos.create({ id: 'b', label: 'Sit amet', done: false })
// => loggerBis: [ 'b' ]

API

createStore<{ t: T }>(...collections: string[]): Store<{ t: Collection<T> }>
Collection<T>.get(id: string): T | null
Collection<T>.getAllIds(): string[]
Collection<T>.get$(id: string): ValueObservable<T | null>
Collection<T>.getAllIds$(): ValueObservable<string[]>
Collection<T>.getAll(): T[]
Collection<T>.getAll$(): ValueObservable<T[]>
Collection<T>.create(item: T): T
Collection<T>.update(id: string, value: Omit<T, 'id'>): T
Collection<T>.patch(id: string, value: Partial<Omit<T, 'id'>>): T
Collection<T>.remove(id: string): void

Gotchas

Item should have a property named id of type string. This is mandatory because we use this property as key accessor to the item.

Data must be immutable. Like Redux, your items should be handled as "immutable data".

Data should not be instanciated. Items should be plain JavaScript object because we use the spread operator to perform update / patch of items.