Higher Order Components

4 min read

No lie I love me some Higher Order Components(HOC)! It makes life so much easier to be able to apply whatever business logic, layout, styling, data, etc to components by wrapping them in an HOC. Think of an HOC as just that: a wrapper for your component that lifts up the logic that would normally be present making it reusable with other components needing the same data, layout, etc. It lends itself to more composable code & less writing of the same logic across multiple files. This very blog uses 2 HOC’s. One for setting the global layout of the application & another for applying Google Analytics throughout all views.

What is an HOC?

A Higher Order Component is in all reality a Higher Order Function; which is nothing more than a function that does one of the following or both: takes in another function as an argument &/or returns a function.

function myHigherOrderFunction(x) {
	return function (y) {
		console.log(x + y)
var AdditionWithHofs = myHigherOrderFunction(2)(4)
console.log(AdditionWithHofs) // returns 6

That syntax might look familiar if you use the connect() method (HOC!) from the React-Redux library:

import React, { Component } from 'react'
import { connect } from 'react-redux'
import { someAction } from '../actions'
class App extends Component {
	async componentDidMount() {
		try {
			await this.props.someAction()
		} catch (e) {
	render() {
		return <SomeHTML />
export default connect(null, { someAction })(App)
 * NOTE: connect() takes two arguments the first being the traditional
 * mapStateToProps() & the second being mapDispatchToProps(). Both of
 * these functions return an object so we can skip creating both and
 * provide instead the object that would be returned.
 * i.e. mapStateToProps => ({ foo: state.bar })
 * i.e. mapDispatchToProps => ({ actions: someAction })

Thinking in React

In React.js components are nothing more than your typical JavaScript function that returns some amount of HTML. This was one of the core concepts applied to Next.js. When writing a page in Next.js you are exporting a function that will return some amount of HTML to the DOM. Our HOC accepts a component which is nothing more than a function so we can wrap the function with the WithLayout HOC and it will return our page with the applied layout settings.

In this short tutorial we will use create-next-app to spin up a Next.js boilerplate in a jiffy so we can get started!

create-next-app hoc-playground
cd hoc-playground && mkdir lib
cd lib && touch index.js WithLayout.js && cd ..
code .

Writing the WithLayout HOC

import { Component } from 'react'
import PropTypes from 'prop-types'
import { loadGetInitialProps } from 'next/dist/lib/utils'
import {
} from '../components'
// Export our function that will take a component as an argument.
export default ComposedComponent =>
	class WithLayout extends Component {
		static propTypes = {
			url: PropTypes.shape({
				pathname: PropTypes.string.isRequired,
		static async getInitialProps(ctx) {
			return loadGetInitialProps(ComposedComponent, ctx)
		render() {
			// Return the component passed to WithLayout wrapped
			// by the following Components for setting the layout.
			// NOTE: <Meta /> is setting global css & all <head></head>
			// related elements.
			return (
					<Meta />
					<Header url={this.props.url.pathname} />
						<ComposedComponent {...this.props} />
					<Footer />

Using the HOC in our Application

import WithLayout from '../lib'
// WithLayout takes the argument of a component
// which is nothing more than a function!
export default WithLayout(() => (
	<div className='home-page'>
		<h1>Hello HOC's in Next!</h1>

Note that I could create a component called HomePage and write the syntax like below, or if you like decorators like I do you can use them as well. Just make sure you are using the proper babel-plugins so they work.

import { Component } from 'react'
import WithLayout from '../lib'
class HomePage extends Component {
export default WithLayout()(HomePage)
import { Component } from 'react'
import WithLayout from '../lib'
export default class HomePage extends Component {

Examples of HOCs in the wild

The next time you see yourself writing a lot of the same business logic code across multiple files in your application it might be time to think about using an HOC instead!

~ Cody 🚀

Related Articles

    Going to the Gopher Side

    The chaos that is the JavaScript/TypeScript ecosystem has become too much to bear in my opinion. I have become unhappy with my direction in the tech industry and in late 2023 made the decision to begin teaching myself Go and pivoting my career out of the Frontend & away from JavaScript.

    Migrating From Yarn To Pnpm

    My experience moving from classic yarn to pnpm as my package manager in JavaScript land.

Cody Brunner

Cody is a Christian, USN Veteran, Jayhawk, and an American expat living outside of Bogotá, Colombia where he works as a Senior Frontend Developer for WAO Fintech.