lux.js

WebJar for lux.js

License

License

MIT
GroupId

GroupId

org.webjars.bower
ArtifactId

ArtifactId

lux.js
Last Version

Last Version

0.7.3
Release Date

Release Date

Type

Type

jar
Description

Description

lux.js
WebJar for lux.js
Project URL

Project URL

http://webjars.org
Source Code Management

Source Code Management

https://github.com/LeanKit-Labs/lux.js

Download lux.js

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.bower/lux.js/ -->
<dependency>
    <groupId>org.webjars.bower</groupId>
    <artifactId>lux.js</artifactId>
    <version>0.7.3</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.bower/lux.js/
implementation 'org.webjars.bower:lux.js:0.7.3'
// https://jarcasting.com/artifacts/org.webjars.bower/lux.js/
implementation ("org.webjars.bower:lux.js:0.7.3")
'org.webjars.bower:lux.js:jar:0.7.3'
<dependency org="org.webjars.bower" name="lux.js" rev="0.7.3">
  <artifact name="lux.js" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.bower', module='lux.js', version='0.7.3')
)
libraryDependencies += "org.webjars.bower" % "lux.js" % "0.7.3"
[org.webjars.bower/lux.js "0.7.3"]

Dependencies

compile (3)

Group / Artifact Type Version
org.webjars.bower : postal.js jar [1,2)
org.webjars.bower : machina jar [1,2)
org.webjars.bower : lodash jar [3,4)

Project Modules

There are no modules declared in this project.

lux.js: Illuminating React

What Is It

lux.js is an implementation of a Flux architecture using ReactJS, postal.js and machina.js. In a nutshell, the React components, dispatcher and stores are highly de-coupled. Here's a gist of the opinions at play:

  • Components use a luxWrapper as a proxy to stores.
  • The lux dispatch method generates message payloads that are routed to the Dispatcher. This coordinates when and how the stores and action listeners are told to handle the actions.
  • Store operations are synchronous.
  • Store state is not mutated directly*. In fact, it's only possible to mutate store state inside a store's action handler. Communication with a store is done via the Dispatcher (by dispatching an action), or an equivalent message-capable API that follows the lux message contracts for these operations.
  • Other modules can take a dependency on a store for read-only operations.
  • Once all stores involved in processing an action have completed their tasks, the Dispatcher signals (via msg) that it's OK for the stores to send change notifications.
  • luxWrapped components (see below) that are wired up to listen to specific stores will receive their updates, etc.
  • All communication happens via message passing.
  • Each message payload should be fully serializable(!)

* Due to not forcing immutable objects, its possible to change state via reference, but the Store apis encourage explicitly getting and setting state and the setState helper is only functional in a store's action handler.

Example Usage

This is a very simple example showing a single store and a lux wrapped component. You can play with this example online.

store.js

import { Store } from "lux.js";

export default new Store( {
	namespace: "light",
	state: {
		light: "off"
	},
	handlers: {
		"toggleLight"() {
			const { light } = this.getState();
			this.setState( {
				light: light === "off" ? "on" : "off"
			} );
		}
	},
	getLightStatus() {
		return this.getState().light;
	}
} );

LightMode.js

import React from "react";
import { luxWrapper, dispatch } from "lux.js";
import lightStore from "./store";

function LightMode({ lightStatus, onToggleLight }) {
	return (
		<div>
			<p>
				Light Status: <b>{lightStatus}</b>
			</p>
			<div className={`light light-${lightStatus}`}>
				<i className="fa fa-lightbulb fa-3x" />
			</div>
			<button onClick={onToggleLight}>Toggle Light</button>
		</div>
	);
}

export default luxWrapper(LightMode, {
	stores: ["light"],
	getState() {
		return {
			lightStatus: lightStore.getLightStatus()
		};
	},
	actions: {
		onToggleLight() {
			dispatch("toggleLight");
		}
	}
});

Development

To build the project:

$ npm install
$ npm run build

Built files appear under /lib in the project root.

To run tests:

npm test

Examples and More:

  • Doug Neiner has created a great example app here.
  • Check out the flux-comparison project so you can see what lux looks like compared to other great flux implementations.
org.webjars.bower

LeanKit Labs

A place to share experimental open source components

Versions

Version
0.7.3