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

atom.undo

v0.5.5

Published

Reactive variables with Undo-Redo

Downloads

14

Readme

Minimalistic Undo-Redo implementation for Atoms.

npm version Build Status

Reference

Import

You must first provide an Atom implementation. You can use either

import Atom from "bacon.atom"

or

import Atom from "kefir.atom"

for example. See bacon.atom and kefir.atom for details.

It is also possible to create atoms in other ways, such as with storage, see atom.storage.

The default import

import Undo from "atom.undo"

is a function to create an undoable atom.

Undoable

To create an undoable atom, you must pass an initial value and the desired Atom constructor:

const undoable = Undo({value: initial, Atom})

The return value is a lensed atom with additional properties for controlling history.

undoable.undo() and undoable.redo()

Undoes or redoes a change (if any).

undoable.undo.count and undoable.redo.count

Observable property that gives the number of times undo or redo has an effect.

undoable.undo.has and undoable.redo.has

Observable property that gives a boolean on whether undo or redo has an effect.

undoable.initial

Observable property that gives the initial value of the undoable.

undoable.reset(value)

Resets the state of the undoable so that the given value becomes the new initial value and all history is dropped.

undoable.revert()

Resets the state of the undoable to the value of undoable.initial and drops all history.

Replace

By default, every actual change (as determined by an acyclic equality predicate) of the value of an undoable atom creates a new history entry. In many cases you don't want to generate history for every change. The Undo constructor takes an optional replace predicate as a parameter, which let's you control when the value is just replaced without creating history.

The replace function is given as a parameter an object of the form {date, value, old: {date}}, where dates have been obtained by Date.now(). If replace returns a truthy value, the latest value is replaced without creating history.

The named import Replace

import {Replace} from "atom.undo"

provides ready made replacement policies for undo.

For example, to create an undoable atom with a 2.5 second history "debounce" period, one could write:

const undoable = Undo({replace: Replace.youngerThan(2500),
                       value: initial,
                       Atom})

Replace.never

The default never policy is to never replace and always generate history.

Replace.youngerThan(periodInMilliseconds)

The youngerThan policy is to replace, without generating history, when the previous entry is younger than the given period in milliseconds.