Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
delorean.js
Advanced tools
DeLorean is a tiny Flux pattern implementation.
Object.observe
to listen store changes,/** @jsx React.DOM */
var Flux = DeLorean.Flux;
// Store
var IncrementStore = Flux.createStore({
actions: {
'increase': 'increaseTotal'
},
total: 0,
increaseTotal: function () {
this.total++;
this.emit('change');
},
getState: function () {
return {
total: this.total
};
}
});
var incrementStore = new IncrementStore();
// Dispatcher
var IncrementDispatcher = Flux.createDispatcher({
increase: function () {
this.dispatch('increase');
},
getStores: function () {
return {
increment: incrementStore
};
}
});
// Action Generator
var IncrementActions = {
increase: function () {
IncrementDispatcher.increase();
}
};
// Component
var IncrementView = React.createClass({
mixins: [Flux.mixins.storeListener],
render: function() {
return <div>
<div>Total: {this.stores.increment.store.total}</div>
<button onClick={this.handleIncrease}>Increase</button>
</div>;
},
handleIncrease: function () {
IncrementActions.increase();
}
});
React.renderComponent(<IncrementView dispatcher={IncrementDispatcher} />, document.body);
Data in a Flux application flows in a single direction, in a cycle:
You can install DeLorean with Bower:
bower install delorean
You can also install by NPM to use with Browserify (recommended)
npm install delorean.js
var Flux = require('delorean.js').Flux;
Stores contain the application state and logic. Their role is somewhat similar to a model in a traditional MVC, but they manage the state of many objects — they are not instances of one object. Nor are they the same as Backbone's collections. More than simply managing a collection of ORM-style objects, stores manage the application state for a particular domain within the application.
Flux.createStore
var TodoStore = Flux.createStore({
todos: [
{text: 'hello'},
{text: 'world'}
],
actions: {
'todo:add': 'addTodo',
'todo:remove': 'removeTodo'
},
addTodo: function (todo) {
this.todos.push({text: todo.text});
this.emit('change');
},
removeTodo: function (todoToComplete) {
this.todos = this.todos.filter(function (todo) {
return todoToComplete.text !== todo.text
});
this.emit('change');
},
getState: function () {
return {
todos: this.todos
}
}
});
initialize
You may define an initialize
function to run something on construction. In construction
status, you may do server actions. But action creators are more simple entity to
do server actions.
var TodoStore = Flux.createStore({
todos: [
{text: 'hello'},
{text: 'world'}
],
initialize: function (url) {
var self = this;
$.getJSON(url, {}, function (data) {
self.todos = data.todos;
self.emit('change');
});
}
});
var myTodos = new TodoStore('/todos');
Array.observe
and Object.observe
, or listenChanges
You don't have to call emit('change')
everytime. You may use observe
feature
of ES.next.
var TodoStore = Flux.createStore({
todos: [
{text: 'hello'},
{text: 'world'}
],
initialize: function (url) {
var self = this;
// It will update store and Views everytime
// you changed the data.
Array.observe(this.todos, function () {
self.emit('change');
});
$.getJSON(url, {}, function (data) {
self.todos = data.todos;
// You don't have to emit 'change' event.
});
}
});
var myTodos = new TodoStore('/todos');
Also you may use listenChanges
method which is doing Array.observe
or Object.observe
already for you.
...
initialize: function (url) {
var self = this;
// It will basically runs `Array.observe` or `Object.observe`
this.listenChanges(this.todos);
$.getJSON(url, {}, function (data) {
self.todos = data.todos;
});
}
...
The dispatcher is the central hub that manages all data flow in a Flux application. It is essentially a registry of callbacks into the stores. Each store registers itself and provides a callback. When the dispatcher responds to an action, all stores in the application are sent the data payload provided by the action via the callbacks in the registry.
Flux.createDispatcher
var TodoListApp = Flux.createDispatcher({
removeTodo: function (todo) {
if (confirm('Do you really want to delete this todo?')) {
this.dispatch('todo:remove', todo);
}
},
getStores: function () {
return {
todoStore: myTodos
}
}
});
dispatch
When an action is dispatched, all the stores know about the status and they
process the data asynchronously. When all of them are finished the dispatcher
emits change:all
event, also dispatch
method returns a promise.
var TodoListApp = Flux.createDispatcher({
removeTodo: function (todo) {
if (confirm('Do you really want to delete this todo?')) {
this.dispatch('todo:remove', todo)
.then(function () {
// All of the stores finished the process
// about 'todo:remove' action
alert('Item removed successfully');
});
}
},
getStores: function () {
return {
todoStore: myTodos
}
}
});
Action creators are the main controller of the app. They are simply objects that manages everything. It allows you to compose data and logic.
var TodoActionCreator = {
getAllTodos: function () {
// It's an example for async requests.
// You can do a server request.
$.getJSON('/todos', function (data) {
TodoListDispatcher.reset(data.todos);
});
},
addTodo: function (todo) {
// It statically calls dispatchers.
TodoListDispatcher.addTodo(todo);
},
removeTodo: function (todo) {
TodoListDispatcher.removeTodo(todo);
}
};
Then you can just run TodoActionCreator.getAllTodos()
function to start Flux cycle.
You may bring all the flow together with the Views, actually the Action generators.
You should use Flux.mixins.storeListener
mixin to get a view into the Flux system.
Also you should pass dispatcher={DispatcherName}
attribute to main React view. It will
pass dispatcher all the child views which have storeListener
mixin.
// Child views don't have to have storeListener.
var TodoItemView = React.createClass({
render: function (todo) {
return <li onClick={this.handleClick}>{this.props.todo.text}</li>
},
handleClick: function () {
TodoActionCreator.removeTodo(this.props.todo);
// or, this.props.dispatcher.removeTodo(this.props.todo);
}
});
var TodoListView = React.createClass({
mixins: [Flux.mixins.storeListener],
render: function () {
var self = this;
return <ul>
{this.stores.todoStore.store.todos.map(function (todo) {
return <TodoItemView todo={todo}></TodoItemView>
})}
</ul>
}
});
storeDidChange
and storesDidChange
Two functions are triggered when a store changed and all stores are changed. You can use these functions if your application needs.
var TodoListView = React.createClass({
mixins: [Flux.mixins.storeListener],
// when all stores are updated
storesDidChange: function () {
console.log("All stores are now updated.");
},
// when a store updates
storeDidChange: function (storeName) {
console.log(storeName + " store is now updated.");
},
render: function () {
// ...
}
});
You can use any Router tool with DeLorean. In the example I use director
as the router.
var Router = require('director').Router;
You may trig the action from View. So you can just do something like that:
var mainView = React.renderComponent(<ApplicationView dispatcher={TodoListDispatcher} />,
document.getElementById('main'))
var appRouter = new Router({
'/random': function () {
TodoActionCreator.addTodo({text: Math.random()});
location.hash = '/';
}
});
There is a simple TodoMVC example working with DeLorean.js
cd examples/todomvc
grunt
open index.html
The flux capacitor was the core component of Doctor Emmett Brown's time traveling DeLorean time machine
FAQs
Flux Library
We found that delorean.js demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.