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 🙏

© 2025 – Pkg Stats / Ryan Hefner

flimsy

v1.1.0

Published

A single-file <1kb min+gzip simplified implementation of the reactive core of Solid, optimized for clean code.

Readme

Flimsy

A single-file <1kb min+gzip simplified implementation of the reactive core of Solid, optimized for clean code.

Check out the annotated source, if you'd like to more in depth understand how Solid works, or if you'd like to write something similar yourself, this should be a good starting point for you.

Comparison

Compared to how Solid's reactivity system actually works there are the following (known) differences:

  • "Only" these functions are implemented: createSignal, createEffect, createMemo, createRoot, createContext, useContext, getOwner, runWithOwner, onCleanup, onError, batch and untrack.
  • createSignal's setter doesn't give you the current updated value inside a batch, but instead gives you the same value that the getter would give you.
  • createEffect doesn't schedule effects, they are executed immediately just like memos. In Solid they are scheduled if they exist inside a root.
  • createEffect and createMemo don't pass the previous execution's return value to your function, just put the value in a variable outside of the function yourself to remember it, if you need that.
  • createContext gives you get/set functions instead of a Provider component, as the Provider component only really makes sense in a UI context and Solid doesn't expose a lower-level context primitive.
  • createContext's set function will register the context value with the parent observer, so you need to create a custom parent observer yourself (which is basically what Provider does), if you need that.
  • Flimsy uses a MobX-like propagation algorithm, where computations in the reactive graph are marked stale/ready, Solid should work similarly, but I don't understand it well enough to know what the differences may be.
  • Flimsy doesn't care about performance nor memory usage, it instead optimizes for clean code.
  • Flimsy is probably buggier, hence the name, though if you'd like to use this in production please open an issue, I'll wire it with oby's extensive test suite.
  • Solid's reactivity system doesn't do anything on the server by default, you'll have to explicitly use the browser build to make it work, Flimsy is isomorphic.

Install

npm install --save flimsy

Usage

You should be able to use these functions pretty much just like you would use Solid's, for example:

import {createSignal, createEffect, createMemo} from 'flimsy';

// Make a counter, a memo from the counter, and log both in an effect

const [count, setCount] = createSignal ( 0 );

const double = createMemo ( () => count () * 2 );

createEffect ( () => {

  console.log ( 'count', count () );
  console.log ( 'double', double () );

});

License

MIT © Fabio Spampinato