skip to content
Notes && Anecdotes
A decorative, semi-related stock photo that adds less value than this comment.

Stop using defaultProps


Question of the day:

Should we use defaultProps, or defaultValues?

// Default values
const Hand = ({ hand = "left" }) => <h1>{left}</h1>;

// Default props
const Hand = ({ hand }) => <h1>{left}</h1>;
Hand.defaultProps = { hand: "left" };


Default values. But you can leave defaultProps alone when you find them in non-functional components, because readability for React class components are better as defaultProps.

Why? Because utilizing the language features is better than utilizing library features (all else equal). And because Dan says defaultProps will be deprecated from React, which is the only reason we use them to begin with.


By spec, default values are re-evaluated on every invocation of the function. defaultProps, on the other hand, are evaluated once and cached at the module level - across every invocation of the function.

This may sound like defaultProps are more performant if you have computationally heavy default args. But that’s so rare I don’t think I’ve ever seen it. A cache isn’t free either, and I doubt caching default values is your best use of a cache?

Performance: whatever.

There are other, better arguments for and against.


When a function becomes large, you can not see default props values when navigating to the function

// Default values: easy to see values immediately
const Hand = ({ hand = 'left' }) => {
  // Many many lines, can't see below

Here’s the same method with defaultProps

// defaultProps: can't see values
const Hand = ({ hand }) => {
  // Many many lines, can't see below

Maybe defaultProps are more readable when you have (too) many props?

// default values: messy method signature
const Body = ({
	ear = "2",
	eye = "brown",
	head = "round",
	nail = "polished",
	toe = "stubbed",
}) => {
	// ...


const Body = ({ arm, ear, eye, head, nail, toe }) => {
	// ...

Body.defaultProps = {
	ear: "2",
	eye: "brown",
	head: "round",
	nail: "polished",
	toe: "stubbed",

defaultProps are more readable for Class components

// default values
class Belly extends React.Component<Props, State> {
  constructor {
    const { moleLocation = 'top right' } = this.props;

  render {
    const { bellybutton = 'outwards' } = this.props;



I’ve found one question regarding Props that I don’t know the answer to:

// Given this class
const Belly = ({
  bellyButton = 'outwards',
  moleLocation = 'top right'
}) => {

// Are these props correct?
// Or should they be optional?
type Props = {
  bellyButton: string,
  moleLocation: string,
  • If you say that they should be required, then the type annotation does not serve as documentation for how to use the class. It then becomes important that your tools understand that they’re not required.

  • If you say that they should be optional, then the type annotation does not tell you what assumptions you can have inside the class. It is then important that your tools understand that they’ll always have values.

Conceptually, I personally I lean towards having them optional. Arguments is “How you instansiate” a class, not “What values are defined” (inside a class). Practically, I’m also more often uncertain about a class when I’m working outside it, than inside it.

And it shouldn’t really matter, as long as your TypeScript compiler or Flow linter and your IDE know what’s going on.


  • Don’t use defaultProps in functional components
  • Let them be the way they are in class components (rewrite the classes first)

If you disagree, watch eslint-plugin-react going to town on each other about this. Others have argued so you don’t have to.