2018-06-25
2093
#react
JuanMa Garrido
224
Jun 25, 2018 â‹… 7 min read

Using Recompose to write clean higher-order components

JuanMa Garrido Freelance JavaScript full-stack developer and trainer | Frontend specialist | From Murcia with love

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 â‹… 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 â‹… 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 min read
View all posts

5 Replies to "Using Recompose to write clean higher-order components"

  1. Excellent article JuamMa and good examples. However, I think you may have forgot to change the code for withHandlerClick.js, as it looks the same as withStateTimes.js unless I have misread it…

  2. looks like there is some copy/paste code errors… look at this file you pasted: withHandlerClick.js (it is not the correct one)

  3. Thanks for the article! It’s very useful if you hear about recompose the first time! But you should mention somewhere that the recompose-library recommend to use hooks instead now. I see that this article is from 2018 and hooks were released in 2019 but this information would help a lot ! 🙂

    “Hi! I created Recompose about three years ago. About a year after that, I joined the React team. Today, we announced a proposal for Hooks. Hooks solves all the problems I attempted to address with Recompose three years ago, and more on top of that. I will be discontinuing active maintenance of this package (excluding perhaps bugfixes or patches for compatibility with future React releases), and recommending that people use Hooks instead. Your existing code with Recompose will still work, just don’t expect any new features. Thank you so, so much to @wuct and @istarkov for their heroic work maintaining Recompose over the last few years.”

    https://github.com/acdlite/recompose

Leave a Reply