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

@exodus/atoms

v9.0.0

Published

Abstraction for encapsulating a piece of data behind a simple unified interface: get, set, observe

Downloads

30,414

Readme

@exodus/atoms

Install

    yarn add @exodus/atoms

What is an atom?

An atom is a data source wrapper that exposes a single piece of data through 3 different methods:

  • get(): read data
  • set(newValue): write data
  • observe(async (data) => {}): observes data changes. Will be called initially with current data value. Observers are awaited in series.
  • reset(): clear the stored value. The next get() call will return the default value* and observers will be called with the default value.

Data sources

This library provides helpers for creating atoms from multiple data sources we use in our apps

| | get | set | observe | | ------------- | ----- | ------- | ------- | | Memory | ✅ * | ✅ | ✅ | | Storage | ✅ | 🟡 ** | ✅ | | Remote config | ✅ | ❌ | ✅ | | Local config | ✅ | ✅ | ✅ | | Event emitter | ✅ | ❌ | ✅ |

* If no defaultValue is provided, a memory atom's get() method will hang and observers will NOT be called until the first set() call.

** A storage atom needs a special isSoleWriter param to allow write access. This is because storage instances can overlap, e.g. a parent namespace can mutate a child namespace, and our storage-spec doesn't currently provide for detecting changes across those instances.

Usage

import { createInMemoryAtom, createStorageAtomFactory, fromEventEmitter } from '@exodus/atoms'

// In memory atoms
const availableAssetNamesAtom = createInMemoryAtom({
  defaultValue: {},
})

// Storage atoms
const storageAtomFactory = createStorageAtomFactory({ storage })

const acceptedTermsAtom = storageAtomFactory({
  key: 'acceptedTerms',
  defaultValue: false,
  isSoleWriter: true,
})

// Event emitter
const geolocationAtom = fromEventEmitter({
  emitter: geolocation,
  event: 'geolocation',
  get: geolocation.get,
})

Helper functions

compute({ atom, selector })

Computes an atom from another by applying a selector function to the observed data source. Returned atom is read-only, i.e. set will fail.

withSerialization({ atom, serialize, deserialize })

Computes an atom from another by serializing it's data after reading it and deserializing it before writing it.