Last updated 8 months ago

BlueChip helps you manage your data in a consistent way when working with client-side JavaScript state management systems.




The Basics

There are only two things that BlueChip does.

  1. Normalize data and organize it in a store.

  2. Retrieve the data from the store and prepare it for use.

What BlueChip Is

State API

BlueChip will take your data, normalize it and place it into a shared resources store. The API on this side is pretty minimal.

updateResources() - Takes an entire payload of resources, normalize it and merge it into the store.

updateResource() - Merges in a single resource into your store

removeResource() - Self explanatory. Yay self documenting code!

And that is it for the State API.

Selector API

This is the meat of BlueChip. The selector API is how you prepare your data to be consumed by components. To select data, BlueChip offers a robust ORM-style syntax complete with models, relationships, filtering, includes and more. You only needs access to the resources store to be able to use the selector api.

Here is an example of using the ORM syntax to select from the store

.where({ active: true })

What BlueChip Is Not


BlueChip is not interested in how you get your data. Fetch it, mock it, import it. However you get your data that is your business. The only requirement is that your data is formatted according to one of the adapters (JsonAPI, GraphQL). If it is not formatted you can write a custom adapter to normalize it.

Client Side Store

BlueChip is agnostic to which client-side state management library you choose to use (Redux, Mobx, Vuex, other). You only need access to a shared resources store for BlueChip to work.

Why BlueChip?

  1. You have multiple data sources (or multiple projects with different data sources) and want to consistently interact with all of them in the same way in your client-side state management systems. You can easily normalize and connect components from GraphQL, JsonAPI and custom formatted API's.

  2. You already have a state manager that you like or is a requirement of a project and do not want to adopt multiple to handle both GraphQL and JSON Rest data.

  3. You would like to keep resources unnessted in your stores for ease of updating, simplicity of mutation schema and ability to easily share resources across your application.

  4. You are familiar with and prefer using ORM's when querying and working with data.

Redux Demo

Demo BlueChip Applicaiton

MobX Demo

Getting Started

To start, choose your state management flavor. This is an example using Redux.

$ npm i -S blue-chip


yarn add blue-chip



Batch update resources:

import { updateResources } from 'blue-chip';
export const fetchChecklists = async (dispatch, state) => {
dispatch({ type: "LOADING_DATA" });
try {
const response = await fetch("/checklists.json");
const payload = await response.json();
updateResources(payload, dispatch);
dispatch({ type: "LOADING_SUCCESS" }); }
catch (error) {
dispatch({ type: "LOADING_ERROR" });

Update a single resource:

import { updateResource } from 'blue-chip';
export const updateTask = ({ id, ...attributes }, dispatch) => {
const resource = { id, attributes, type: "tasks" };
updateResource(resource, dispatch);


import { combineReducers } from "redux";
import { resourcesReducer as resources } from 'blue-chip';
export default combineReducers({resources});


Just like any other ORM you will be defining model classes:

import { BaseModel } from "blue-chip";
import Task from "./Task";
export default class Checklist extends BaseModel {
static get hasMany() { return [Task]; }
import { BaseModel } from "blue-chip";
import Checklist from "./Checklist";
export default class Task extends BaseModel {
static get belongsTo() { return [Checklist]; }


const mapStateToProps = state => {
const { resources } = state;
return {
loading: state.dataReducer.loading,
error: state.dataReducer.error,
checklists: Checklist.query(resources)
const mapDispatchToProps = dispatch => ({
updateTask: task => updateTask(dispatch, task)
export default connect(mapStateToProps, mapDispatchToProps)(Container);

Store Structure

The resources store is structured as an object with top-level keys as pluralized resource names.

const store = {
resources: {
checklists: {},
tasks: {}

Each resource key points to an object that contains ids as keys and an JSON api object as a value.

const store = {
checklists: {
1: {
id: 1,
attributes: { name: "Oboarding" },
links: { self: "" },
relationships: {
tasks: {
data: [{ id: 1, type: "tasks: }, { id: 2, type: "tasks: }],
type: "checklists"
tasks: {

Project Status

This project is currently in Alpha/Experimental phase. The APIs will almost assuredly change prior to 1.0. It is not ready for production yet so use at your own risk. There are also unfinished features like MobX adapter


  1. belongsTo relationship

  2. Add Unstated adapter

  3. Change API to be more modular to allow for configuring adapters

  4. Memoization