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

xstate-undoable

v0.0.2

Published

Undo behaviour for xState machines

Downloads

5

Readme

xstate-undoable

A wrapper to augment simple xState machines (not interpreted machines) with go-back behaviour.

Motivation/Drawbacks

While xState solved a lot of problems for me, not being able to go back in state history was a big deal-breaker. I had to extend the library to allow me to travel back in time. That's why I created this little wrapper around xState, which adds the pieces that were missing for me: going back, resetting the machine and retrieving the state machine's history.

How is this different from History states?

History nodes allow you to transition back to the previous sub-state of a state node, but you can't go back any further in history.

Drawbacks

Be aware that this wrapper is stateful, storing the state machine's history in an internal array. This is contrary to what a simple non-interpreted state machine does, which is fully pure and doesn't store any internal state.

This conflicts with the way that transition works (which is pure) since we're augmenting its behaviour to store its result. But this was an acceptable drawback for my use case, and I may consider extending this library with a pure version in the future.

This also means you can't use interpreted machines with go-back behaviour, because there's no way to send a goBack event to the interpreted state machine yet. I might try to implement this feature at some point in the future.

Installation

npm install xstate-undoable
yarn add xstate-undoable

Usage

Setup your xState state machine as usual:

const forwardMachine = createMachine({
  id: 'forward',
  initial: 'one',
  states: {
    one: { on: { FORWARD: { target: 'two', actions: 'increment' } } },
    two: { on: { FORWARD: 'three' } },
    three: { type: 'final' }
  },
});

Then pass it into this wrapper:

import undoableStateMachine from 'xstate-undoable';

const undoable = undoableStateMachine(forwardMachine);

// moving forward
undoable.transition('one', 'FORWARD');

// go back on step
const previousState = undoable.goBack();

// => 'one'

API

goBack()

Goes back one step in state history

undoable.transition('one', 'FORWARD');
const previousState = undoable.goBack();
// => 'one'

reset()

Sets the state machine back to its initial state

const initialState = undoable.reset();
// => 'one'

getHistory()

Returns the state machine history as an array

const stateOne = undoable.transition(state.initial, 'FORWARD');
const stateTwo = undoable.transition(state.value, 'FORWARD');
const history = undoable.getHistory();
// => ['one', 'two']

License

MIT