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

@rbxts/fsm

v1.0.0

Published

Generic finite state machine implementation for roblox-ts.

Downloads

8

Readme

FSM (Finite State Machine)

A super simple finite state machine pattern implementation. If you are not sure what this is, a finite state machine is a state manager that ensures a system is only in a single state out of a predefined, finite number of states at one time, and has a set of predefined paths that it can take.

Example

In this example, this traffic light loops between each state forever. Because we defined the possible transitions in the transitions variable, we know that the machine can ONLY go in the sequence we defined.

If the ORANGE_OFF event is fired when the light is GREEN, the event is just ignored since there is no transition defined for such a scenario, this way we can ensure our system always follows a predictable and predefined pattern.

enum State {
	GREEN,
	ORANGE,
    RED,
}

enum Event {
	GREEN_OFF,
	ORANGE_OFF,
	RED_OFF,
}

const transitions: Transition<State, Event>[] = [
    // When the GREEN_OFF event fires, and we're in the GREEN state, switch to ORANGE
	{ event: Event.GREEN_OFF, from: State.GREEN, to: State.ORANGE },

    // When the ORANGE_OFF event fires, and we're in the ORANGE state, switch to RED
	{ event: Event.ORANGE_OFF, from: State.ORANGE, to: State.RED },

    // When the RED_OFF event fires, and we're in the RED state, switch back to GREEN
	{ event: Event.RED_OFF, from: State.RED, to: State.GREEN },

    // Create more states, events, transitions... get as complex as you want
];

const trafficLight = new FiniteStateMachine(State.GREEN, ...transitions);

trafficLight.onState(State.GREEN, () => {
	print('THE LIGHT IS GREEN');
	task.delay(2.5, () => trafficLight.processEvent(Event.GREEN_OFF));
});

trafficLight.onState(State.ORANGE, () => {
	print('THE LIGHT IS ORANGE');
	task.delay(1, () => trafficLight.processEvent(Event.ORANGE_OFF));
});

trafficLight.onState(State.RED, () => {
	print('THE LIGHT IS RED');
	task.delay(2.5, () => trafficLight.processEvent(Event.RED_OFF));
});

// Since the initial state was defined GREEN, the system is currently
// in the GREEN state, so the only event that will do anything is GREEN_OFF
trafficLight.processEvent(Event.GREEN_OFF);