This standalone javascript micro-framework provides a finite state machine for your pleasure.

* You can find the [code here](https://github.com/jakesgordon/javascript-state-machine)

* You can find a [description here](http://codeincomplete.com/posts/2013/1/26/javascript_state_machine_v2_2_0/)

* You can find a [working demo here](http://codeincomplete.com/posts/2011/8/19/javascript_state_machine_v2/example/)

Using npm:

Or download the source from [state-machine.js](https://github.com/jakesgordon/javascript-state-machine/raw/master/state-machine.js),

or the [minified version](https://github.com/jakesgordon/javascript-state-machine/raw/master/state-machine.min.js)

In its simplest form, create a standalone state machine using:

* fsm.cannot(e) - return true if event `e` cannot be fired in the current state

* fsm.transitions() - return list of events that are allowed from the current state

If an event is allowed **from** multiple states, and always transitions to the same

state, then simply provide an array of states in the `from` attribute of an event. However,

the same name if you prefer the verbose approach.

4 types of callback are available by attaching methods to your StateMachine using the following naming conventions:

* return `false` from an `onleaveSTATE` handler to cancel the event.

* return `ASYNC` from an `onleaveSTATE` handler to perform an asynchronous state transition (see next section)

Sometimes, you need to execute some asynchronous code during a state transition and ensure the

new state is not entered until your code has completed.

You can also turn all instances of a _class_ into an FSM by applying

the state machine functionality to the prototype, including your callbacks

ensure that each instance constructed is initialized with its own unique `current` state._

How the state machine should initialize can depend on your application requirements, so

the library provides a number of simple options.

that each instance gets its own unique `current` state, rather than an (unwanted) shared

`current` state on the prototype object itself._

By default, if you try to call an event method that is not allowed in the current state, the

state machine will throw an exception. If you prefer to handle the problem yourself, you can

]});

alert(fsm.calm()); // "event calm was naughty :- event not allowed in current state green"

See [RELEASE NOTES](https://github.com/jakesgordon/javascript-state-machine/blob/master/RELEASE_NOTES.md) file.

See [LICENSE](https://github.com/jakesgordon/javascript-state-machine/blob/master/LICENSE) file.

If you have any ideas, feedback, requests or bug reports, you can reach me at

[jake@codeincomplete.com](mailto:jake@codeincomplete.com), or via

my website: [Code inComplete](http://codeincomplete.com/)