Aug 4, 2018 · 3 min read

TL;DR: Static properties are properties of a class, not of an instance of a class.

In university, I was taught object-oriented programming in Java. Like most beginners, the first thing I learned was some version of this:

A “Hello, World” program written in Java.

Getting started, I was confused by all these keywords. public, static, void, String, etc… What are all these things!?

Eventually, I learned the meaning behind most of these keywords and how to use them through passive exposure. public makes a class or method available to be used by other programs, void is a type of none, String is an array of chars. These all came naturally as I wrote more Java code. However, static remained a mystery to me for years to come. It simply didn’t come up that often in assignments and projects (except for in that boilerplate main Java method shown above) so there was never a real need to learn its meaning.

When I started learning React a couple years ago I started seeing static and began interacting with it more actively. Here’s an example:

Example of static properties in a React component.

Over time, static subconsciously worked it’s way into my development vocabulary, but I still didn’t know why I was using it. I would use it with defaultProps, propTypes, contextTypes, and displayName, and I just assumed it needed to be there for some syntactic reason. I was following patterns that I saw on StackOverflow, and in docs without stopping to think about what static means.

Then I saw a neat example defining state without a constructor:

A React component with state and no constructor.

In previous examples I’d seen, state was always defined in the constructor of a class, so it caught my interest when I realized state could be defined without a constructor. I also noticed that state isn’t preceded by static which prompted the question: What the heck does static actually do?

And after a quick Google search, I had my answer…

Static properties are properties of a class, not of an instance of a class.

Let’s break that down a bit with an example.

If we have two instances of a React component Foo, the displayName, propTypes, defaultProps will remain the same across both instances, but the state of each instance will be able to update independently of one another.

thisFoo will have a state and thatFoo will have a state, but both share the same static properties — displayName, propTypes, and defaultProps— from the class definition.

A Deeper Understanding

This story just scratches the surface of how static is implemented in JavaScript. In reality, the entire class syntax in JavaScript is an abstraction of prototypes.

Rather than fumbling my way through an explanation of prototypes, you can learn more about how classes are implemented in JavaScript here: Classes — The Modern Javascript Tutorial.



Frontend Weekly

It's really hard to keep up with all the front-end…


Written by


I’m an artsy software engineer. I write about JavaScript/React, and sometimes my opinions about other things. ¯\_(ツ)_/¯

Frontend Weekly

It's really hard to keep up with all the front-end development news out there. Let us help you. We hand-pick interesting articles related to front-end development. You can also subscribe to our weekly newsletter at http://frontendweekly.co

More From Medium

More from Frontend Weekly

More from Frontend Weekly

More from Frontend Weekly

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade