
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
xstate-undoable
Advanced tools
A wrapper to augment simple xState machines (not interpreted machines) with go-back behaviour.
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.
npm install xstate-undoable
yarn add xstate-undoable
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'
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']
MIT
FAQs
Undo behaviour for xState machines
The npm package xstate-undoable receives a total of 2 weekly downloads. As such, xstate-undoable popularity was classified as not popular.
We found that xstate-undoable demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.