Idiomatic, modular, testable, isomorphic Flux. No singletons required.
$ npm install --save flummox
- No singletons = isomorphism for free!
- Robust yet minimal API inspired by React and ES6
- The dispatcher and constants are implementation details — no need to interact with them unless you want to.
- Easy integration with React via FluxMixin and FluxComponent
- Support for plain JavaScript class components in React 0.13.*
- Straightforward optimistic UI updates
- Serialization/deserialization of stores, for faster page loads.
- "It's Just JavaScript" — supports CoffeeScript, TypeScript, and any other compile-to-JS language.
*Not officially supported until stable 0.13 release, but it should work
Here's a WIP demo of an isomorphic app using Flummox, React Router, and Immutable.js (still needs some work, but feel free to check it out):
https://github.com/acdlite/flummox-isomorphic-demo
There are sooo many Flux libraries out there. What makes Flummox special?
Flummox allows you to encapsulate your entire Flux set-up — stores, actions, constants, and the dispatcher — into a single class, with zero singletons or global references. It's as easy as
let flux = new Flux();There are many benefits to this approach, but the biggest one is that it makes isomorphism (running the same code on both the server and the client) incredibly straightforward.
Flummox is not a framework. Rather than forcing a bunch of new concepts and complicated APIs upon you, Flummox embraces existing idioms from Flux, React, and ES6 — without being too prescriptive.
tl;dr Show me the code!!! No problem. Check out a full example from Flummox's test suite.
If you know Flux, you know Flummox. If you're not familiar with Flux, there are many great resources available to get you up to speed.
The primary goal of Flummox is reduce the boilerplate involved in setting up Flux for your application, so the API has been kept as minimal and predictable as possible. It uses Facebook's dispatcher under the hood. It encourages (but does not require) the use of ES6 classes. The state API for stores mirrors the state API for React components. Everything works as you'd probably expect. And like React, Flummox prints helpful warning messages to keep you on track. For instance, if you call Store#setState() from outside a store's action handler, you get this warning:
Store#setState() called from outside an action handler. This is likely a mistake. Flux stores should manage their own state.
There are three classes in Flummox: Store, Actions, and Flux. They are completely independent from each other. For example, you can create a new Store without ever touching Flux or Actions. You can extend them, modify them, add mixins — if it's possible with JavaScript, you can do it.
Examples in this document use ES6 class notation, but that's a pattern, not a requirement: underneath the hood, it's just JavaScript prototypical inheritance. It's compatible with CoffeeScript, TypeScript, and regular ES5 right out of the box.
Because Flummox does not rely on singletons, and each of the different classes can be instantiated independently from the others, it's really easy to write tests. A good example can be found in Flummox's own test suite.
This is a big one, and one of the biggest motivating factors for creating this library. Isomorphism is tricky or impossible in many other Flux libraries because they rely on singleton objects, spread out across multiple modules. Often they force you to use a separate API.
Again, because Flummox does not rely on singletons, you get isomorphism for free: just create a new Flux instance on each request! Here's a very basic example how that might look using Express and React:
// shared/Flux.js
class Flux extends Flummox { ... }
// server/app.js
app.get("/", function(req, res) {
let flux = new Flux();
res.send(
React.renderToString(<App flux={flux} />)
);
});Flummox also gives you the ability to serialize the initial state of your application on the server, send it down to the client as a string, and deserialize it before the initial render. While not required for isomorphism, it helps make the initial page load snappy by reducing unnecessary AJAX requests to the server.
Integrating Flummox with React is really easy. You can do it the long way by manually adding and removing event listeners, but that leads to a lot of boilerplate. Use FluxComponent and/or FluxMixin to subscribe to store changes.
Here's a basic example:
import FluxComponent from 'flummox/component';
class OuterComponent extends React.Component {
render() {
return (
// Pass an array of store keys, or a map of keys to state getters
<FluxComponent connectToStores={['storeA', 'storeB']}>
<InnerComponent />
</FluxComponent>
);
}
}Read all about it in the React integration guide.
Flummox is still quite new, but the core features are already in place. A big focus right now is improving the documentation, writing guides, and providing examples. Since Flummox's core innovation is its approach to isomorphism, I would like to make it especially easy for newcomers to learn how to use Flummox to create isomorphic applications.
Feature requests and PRs are absolutely welcome, as long as they keep with the spirit of a minimal core API. Any additional features (e.g. undo-redo & versioning) are likely to be implemented as addons, rather than as part of the core.
Flummox is just Flux. It has no opinion on the rest of your stack. You don't even have to be using React. But in case you're interested, here are some recommended tools and libraries that complement Flummox well:
- React (of course!)
- Immutable.js — Using immutable data in your applications not only makes your application more performant, but it also simplifies state management in your stores. No more defensive copying! It also helps ensure isolation between stores by reducing the likelihood that you'll accidentally mutate a dispatched payload.
- React Router — A complete routing solution for React, with excellent support for isomorphic applications.
- superagent — An isomorphic AJAX library. Use it for all your data fetching.
- Babel — Use next-generation JavaScript (ES6, and even some ES7) today. Once you've tried it, it's the only way to write JavaScript. Babel also very conveniently supports JSX compilation.
- Facebook, obviously.
- Pete Hunt's talk at React.js Conf 2015 "Full Stack Flux". The idea of stores as essentially "a reduce() + a change event" was illuminating.
- alt, a similar Flux library from which I shamelessly copied (ideas, not code)
MIT
Andrew Clark @acdlite