React Binding Patterns: 5 Approaches for Handling `this`

JavaScript’s this keyword behavior has confused developers for ages.

Coding with binds is tricky.

There are at least five ways to handle the this context in React. Let’s consider the merits of each approach.

1. Use React.createClass

If you use React.createClass, React autobinds all functions to this. So the this keyword is bound to your component’s instance automatically:

// This magically works with React.createClass
// because `this` is bound for you.

However, with the advent of ES6 classes, this non-standard approach to creating classes isn’t the future of React. In fact, createClass is likely to be extracted from React core in a future release.

2. Bind in Render

The rest of these approaches assume you’re declaring React components via ES6 classes. If you use an ES6 class, React no longer autobinds. One way to resolve this is to call bind in render:


This approach is terse and clear, however, there are performance implications since the function is reallocated on every render. This sounds like a big deal, but the performance implications of this approach are unlikely to be noticeable in most apps. So ruling this out at the start for performance reasons is a premature optimization. That said, here’s an example where the performance impact of this approach mattered.

Bottom-line, if you’re experiencing performance issues, avoid using bind or arrow functions in render.

3. Use Arrow Function in Render

This approach is similar to #2. You can avoid changing the this context by using an arrow function in render:

onChange={e => this.handleChange(e)}

This approach has the same potential performance impact as #2.

The alternative approaches below are worth considering because they offer superior performance for little extra cost.

4. Bind in Constructor

One way to avoid binding in render is to bind in the constructor (the other approach is discussed in #5 below).

constructor(props) {
this.handleChange = this.handleChange.bind(this);

This is the approach currently recommended in the React docs for “better performance in your application”. This is also the approach I use in “Building Applications with React and Redux in ES6” on Pluralsight.

However, on most apps the performance implications of approach #2 and #3 won’t be noticeable, so the readability and maintenance advantages of approach #2 and #3 may outweigh performance concerns in many apps.

But if you’re willing to use stage-2 features, the final option below is likely your best bet.

5. Use Arrow Function in Class Property

This technique relies upon the proposed class property feature. To use this approach, you must enable transform-class-properties or enable stage-2 in Babel.

handleChange = () => {
// call this function from render
// and this.whatever in here works fine.

This approach has multiple advantages:

  1. Arrow functions adopt the this binding of the enclosing scope (in other words, they don’t change the meaning of this), so things just work automatically.
  2. It avoids the performance issues of approaches #2 and #3.
  3. It avoids the repetition in approach #4.
  4. It’s straightforward to refactor from the ES5 createClass style into this style by converting relevant functions into arrow functions. In fact, there’s a completely automated way to handle this using a codemod.


This flowchart that sums up the decision.

Here are full working examples of all 5 approaches:

So what do people prefer? Here’s the poll:

Have other ways you handle this? Please chime in via the comments.

Huge thanks to @dan_abramov, @kentcdodds, and @dmosher for their valuable input and review!

Cory House is the author of “Building Applications with React and Redux in ES6”, “Building Applications with React and Flux”, “Clean Code: Writing Code for Humans” and multiple other courses on Pluralsight. He is a Software Architect at VinSolutions, Microsoft MVP, and trains software developers internationally on software practices like front-end development and clean coding.