Enter Your Email Address to Watch This Lesson

Your link to unlock this lesson will be sent to this email address.

Unlock this lesson and all 1046 of the free egghead.io lessons, plus get JavaScript content delivered directly to your inbox!

Existing egghead members will not see this. Sign in.

Redux: Store Methods: getState(), dispatch(), and subscribe()

3:09 JavaScript lesson by

We will learn about the Redux Store and demonstrate how its three methods let us implement a counter application.

Get the Code Now
click to level up

egghead.io comment guidelines


We will learn about the Redux Store and demonstrate how its three methods let us implement a counter application.


Create class. There's an error in the transcript, where "chore" is present instead of "store", and "create chore" instead of "createStore".

In reply to egghead.io

just to clarify, is the state being stored in the "store" instance?

I added Redux to our application as a script tag from CDNJS. This is the UMG build, so it exports a single global variable called Redux, with a capital R. In real applications, I suggest you to use npm instead and a module bundler like webpack or Browserify, but the UMG build will suffice for our example.

I'm going to need just a single function from Redux called createStore. I'm using ES6 destruction syntax here. It's equivalent to writing, var createStore = Redux.createStore or, if you use NPM and something like Babel to transpile your ES6, you can write, import { createStore }, notice the bracers, from Redux.

const { createStore } = Redux;
// var createStore = Redux.createStore;
// import { createStore } from 'redux';

This store binds together the three principles of Redux. It holds the current application's state object. It lets you dispatch actions. When you create it, you need to specify the reducer that tells how state is updated with actions.

In this example, we're calling createStore with counter as the reducer that manages the state updates. This store has three important methods.

const store = createStore(counter);

console.log(store.getState());  // 0

The first method of this store is called getState. It retrieves the current state of the Redux store. If we were on this, we're going to see 0 because this is the initial state of our application.

The second and the most commonly used store method is called dispatch. It lets you dispatch actions to change the state of your application. If we log this store state after dispatch, we're going to see that it has changed.

store.dispatch({ type: 'INCREMENT' });
console.log(store.getState());  // 1

Of course, always log into the console gets boring, so we're actually going to render something to the body with the help of the third Redux store method, called subscribe. It lets you register a callback that the Redux store will call any time an action has been dispatched, so that you can update the UI of your application. It will reflect the current application state.

store.subscribe(() => {
  document.body.innerText = store.getState();

document.addEventListener('click', () => {
  store.dispatch({ type: 'INCREMENT' });

I'm being very naive now. I'm not using React or anything. I'm just rendering the counter into the document body. Any time the body is clicked, I'm going to dispatch an action to increment this counter.

If you pay close attention, you will notice that the initial state, the 0, was not rendered. This is because I'm rendering inside the subscribe callback, but it doesn't actually fire the very first time.

Subscribe Method

So I extract this logic into render method. I subscribe the render method to this store. I also call it once to render the initial state. Now it renders the 0, and the click increments the counter. This is our first working Redux application.

const render = () => {
  document.body.innerText = store.getState();

Joel's Head
Why are we asking?