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

fluky

v0.1.22

Published

Framework for flux data flow pattern

Downloads

17

Readme

Fluky

Everything is asynchronous event!

A framework with flux data flow pattern and ECMAScript 6+. With Fluky, asynchronous event is a simple way to control all of frontend data flow. Inspired by Koa, Fluky dispatcher and event handlers were implemented by ES6 generator.

NPM

Installation

Install fluky via NPM:

npm install fluky

Note that fluky is using require and EventEmitter of Node.js, you must have browserify or webpack to make it work for front-end purpose.

Usage

With Fluky, event-driven approach is the only way to handle actions and stores, it makes everything easy and simple.

Actions and Stores implementation

Here is sample code below to show how to implement actions and stores with Fluky and ES5/ES6+:

import Fluky from 'fluky';
  
// ACTION
Fluky.on('action.Todo.toggle', function *(todo) {
  if (todo.completed)
    Fluky.dispatch('store.Todo.unmark', todo.id);
  else
    Fluky.dispatch('store.Todo.mark', todo.id);
});

// STORE

// Getting current state. Initialize state if state doesn't exist.
var todoStore = Fluky.getState('Todo', {
  todos: [];
});

Fluky.on('store.Todo.unmark', function *(id) {

  // Find specific todo item with id
  for (var index in todoStore.todos) {
    var todo = todoStore.todos[index];
    
    if (todo.id == id) {
      // Unmark
      todo.completed = false;
      
      // Fire event that store was changed
      Fluky.dispatch('store.Todo', 'change');
      break;
    }
  }
});

Fluky.on('store.Todo.mark', function *(id) {

  // Find specific todo item with id
  for (var index in todoStore.todos) {
    var todo = todoStore.todos[index];
    
    if (todo.id == id) {
      // Mark
      todo.completed = true;
      
      // Fire event that store was changed
      Fluky.dispatch('store.Todo', 'change');
      break;
    }
  }
});

Fluky.on('store.Todo.create', function *(text) {

  // Add a new todo item to store
  todoStore.todos.push({
    id: Date.now(),
    text: text,
    completed: false
  });
  
  // Fire event that store was changed
  Fluky.dispatch('store.Todo', 'change');
});

If no action defined, message will be forwarded to store. For instance, action.Todo.create isn't defined but forwarding to store.Todo.create automatically.

Access Actions and Stores with React.js

Call action and get data from store both works by using Fluky.dispatch() to fire event.

import React from 'react';
import Fluky from 'fluky';

// React component (view)
class TodoList extends React.Component {

  constructor() {
    // preparing state to initialize component
    this.state = {
		todos: Fluky.getState('Todo').todos;
	};
  }
  
  componentDidMount() {
    Fluky.on('store.Todo', Fluky.bindListener(this.onChange));
  }
  
  componentWillUnmount() {
    Fluky.off('store.Todo', this.onChange);
  }

  // Using "() =>" to bind "this" to method
  onChange = () => {

    // Updating state
    this.setState({
      todos: Fluky.getState('Todo').todos;
    });
  }

  create = () => {
    // Fire event to create a new todo item
    Fluky.dispatch('action.Todo.create', 'Dance');
  }
  
  render: function() {
    var todoList = [];
    
    this.state.todos.forEach((todo) => {
      todoList.push(<div>{todo.text}</div>);
    });
  
    // Template for React
    return (
      <div>
        {todoList}
        <button onClick={this.create}>Add Item</button>
      </div>
    );
  }
}

Modular

You can create a Store without ever touching Action. Fluky provide a way to extend, using Fluky.load() to load Actions and Stores.


import Fluky from 'fluky';

var todoStore = function *() {
  this.on('store.Todo.completeTodoItem', function *() { ... });
  this.on('store.Todo', function *() { ... });
};

Fluky.load(todoStore);

Loading multiple modules at one time is possible:

var actions = [
  todoAction,
  userAction
];

var stores = [
  todoStore,
  userStore
];

Fluky.load(actions, stores);

State Management

In order to make an isomorphic app, initial state should be rendered on the server stage. That's a big challenge because state provided by server usually conflicts with client-side store. Fluky supports state management that a way to solve multiple stores problem.

On the server-side, developer can use setInitialState() to create a initial state:

Fluky.setInitialState({
	Todo: {}
});

Then you can get state with getState() everywhere, modify it and add put stores in it. For example below:

Fluky.getState('Todo').timestamp = Date.now();

In module, it is possible to get Fluky with this keyword, then there is the same way to access state:

var todoStore = function *() {
	this.getState('Todo').timestamp = Date.now();
};

Demo

Just like other front-end framework, fluky has an TodoMVC example for demostration as well.

Change working directory then initializing and starting it with NPM command:

cd examples/todomvc/
npm install
npm start

Now you can open index.html with browser immediately.

Authors

Copyright(c) 2015 Fred Chien <[email protected]>

License

Licensed under the MIT License