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

refacts

v0.0.1

Published

A state container built on facts

Downloads

4

Readme

Refacts

A state container built on facts

Motivation

Current solutions for application state are too imperative.

As an example consider a Todo app using Redux:

  • user submits todo
  • an action is dispatched to add a todo
  • each reducer compares the action type (a string constant) to its own string constants
  • once the todo list reducer is reached (mathcing its type) it puts the todo at the head of a list concating the previous list
  • the store observes a change, updating its subscribers
  • a subscriber will receive the update by selecting a hard coded fragment of the state
  • if that fragment has changed those changes will be reflected
  • if it hasn't changed that will also be reflected, this depends on how naive the subsriber is

This explodes in complexity for an sufficiently advanced app. It also largely has little to do with the intent of the user.

An idealized example:

  • user submits todo
  • a fact is created, there exists a todo(x)
  • known subsets matching this fact are notified
  • a subscriber of a known subset reflects the changes

We reify the fact as a member of subsets, these subsets provide identiy criteria for membership.

A sandpaper grade rough example:

/**
 * Kind
 * Instantiation has the intrinsic properties of `created`, `updated`, `deleted`,
 *
 * These properties are reified as attributes:
 *   createdAt, updatedAt, and deletedAt
 *
 * The intuitive Quality of these properties is temporal, so they can be used
 * in a formal relation such as ordering by recently updated
 *
 * The semantics for a change to an instance are Create, Update, Delete, as in:
 *   todo = Create(Todo, { text: 'new text'})
 *   todo = Update(todo, { text: 'updated text'})
 *   todo = Delete(todo)
 */

set(
  Kind(
    'Todo', Attributes({ text: String })),
  MaterialRelation(
    'Completed', Predicate('complete')),
  FormalRelation(
    'Newer', Predicate('created')),
  Subset(
    'CompletedTodos', Kind('Todo'), Predicate('complete')),
  Subset(
    'RecentTodos', Kind('Todo'), Order('Newer')),
  Subset(
    'RecentCompletedTodos', Intersect('RecentTodos', 'CompletedTodos'))
)

set.getState() === {
  RecentTodos: [],
  CompletedTodos: [],
  RecentCompletedTodos: []
}

set.add(
  Create(Todo, { text: 'This is a todo' }))

set.getState() === {
  RecentTodos: [
    { text: 'This is a todo',
      isComplete: false,
      isNotComplete: true,
      createdAt: '...',
      deletedAt: '...'
    }
  ],
  CompletedTodos: [],
  RecentCompletedTodos: []
}

This project is inspired by the work on DOLCE and OntoClean by Nicola Guarino et al.