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

@thadeu/nanomachine

v1.0.5

Published

🔐 nanomachine is a state machine for tiny JS with < 2 Bytes

Downloads

3

Readme

nanomachine

NPM package version Build Status Size Issues License: MIT


🔐 nanomachine is a state machine for tiny JS

How to install

yarn add @thadeu/nanomachine

or

npm i @thadeu/nanomachine

or unpkg load script

<script src="https://unpkg.com/@thadeu/nanomachine"></script>

Usage


const machine = nanomachine({
  initial: 'login',
  transitions: [
    { name: 'login', from: '*', to: 'login' },
    { name: 'waiting', from: ['login', 'unpause'], to: 'waiting' },
    { name: 'pause', from: ['waiting'], to: 'pause' },
    { name: 'unpause', from: ['pause'], to: 'waiting' },
  ],
  events: {
    login: () => null,
    waiting: () => null,
    pause: () => null,
    unpause: () => null,
  },
})

With a state machine started, you have access to dynamically created methods. Like for example.

If you want to leave login and go to waiting, you can use.

// state is login, right?
machine.waiting()

Everything is based on the transition from to to was configured

{ name: 'waiting', from: ['login', 'unpause'], to: 'waiting' }

In the case above, we say, waiting, you can transition from login or pause to waiting Of course, it will only happen, if there is a method created in events.

The above transition must have a method to be triggered when moving, example:

const machine = nanomachine({
  ......
  events: {
    waiting: () => console.log('fired waiting')
  }
  ......
})

The waiting event, will be invoked whenever the transition is approved in the state machine

Conditionals

Imagine the following situation, you need to change state, only after resolving something. So!

const machine = nanomachine({
  ......
  transitions: [
    { name: 'login', from: '*', to: 'login' },
    { name: 'waiting', from: ['login', 'unpause'], to: 'waiting', if: () => true | false },
  ],
  ......
})

or use unless.

{ name: 'waiting', from: ['login', 'unpause'], to: 'waiting', unless: () => true }

On Any Transition

You can use observers, for example

const machine = nanomachine({
  ....
})

machine.on('waiting', function() {
  console.log('onWaiting')
})

Whenever a waiting transitions occurs, this observer receives a message

Contributing

Once you've made your great commits (include tests, please):

  1. Fork this repository
  2. Create a topic branch - git checkout -b my_branch
  3. Push to your branch - git push origin my_branch
  4. Create a pull request

That's it!

Please respect the indentation rules and code style. And use 2 spaces, not tabs. And don't touch the version thing or distribution files; this will be made when a new version is going to be released.

License

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.