Swizec Teller - a geek with a hatswizec.com

    Custom react hooks ❤️

    This is a story full of wonderful new possibilities, beautiful codey things, and components clean as the mountain air. All thanks to custom react hooks ❤️

    While livecoding on the ThreadCompiler project yesterday, I noticed that with hooks our logic was getting tied up with presentation. All state was local, all logic inside components, shared state was weird, and our components looked like crap.


    Here's an example.

    A component that takes user input from React Context using Constate, passes it through a Remark compiler, then puts the result back in context (so other components can use it), and renders the result locally.

    Local result for user preview, context for TweetButton so we can send it into the world.

    techletter app screenshot 1549905697157

    What a mess 🤮

    We have a rendered state and its setter, then a useEffect that runs on value changes. Passes value through Remark with custom plugins and gets the result.

    Result goes into local state via setRendered, triggering a re-render showing a user preview. Result also goes into context with setOutput which triggers a re-render in <TweetButton> making it ready to tweet things out. ugh

    TweetButton is even worse …

    techletter app screenshot 1549905819350

    We have 3 local states for success, error, and API result. A whole API call function, and some rendering. All inside this poor little component that's supposed to be a button.

    Oy vey 🙄

    How to fix your mess with a custom hook

    We can clean this up with custom hooks.

    Custom hooks are functions built on top of basic React Hooks. You can build them anywhere in your project, use them in a component, and it just works. 👌

    Starting with the <Tweet> component, we can take out all that logic and wrap it in a new function.

    techletter app screenshot 1549905842949

    It's customary to prefix your hooks with use. I like to put them in a directory.

    We now have a useRemark hook with local state and an effect. When input changes it runs through renderTweet. The promise result goes into state. We return the current rendered state.

    Extracting the Remark stuff itself into a renderTweet method makes it easier to use in <TweetButton>. You'll see.

    This new custom hook makes <Tweet> the sweet little component it was always meant to be.

    techletter app screenshot 1549905865408

    Beautiful ❤️

    Something similar happens when we extract the <TweetButton> mess into a hook. Check this out 👇

    Custom hook

    techletter app screenshot 1549905887363

    Almost same code as before.

    You've got your 3 local states, and your sendTweets function. Moved the actual API call to a separate sendTweet function to clean up some more.

    Upon success we update the array of tweet responses, update error and success states, etc.

    The hook returns an object with everything your component needs to use it. List of tweets, current error, the success state, and a sendTweets method.

    Your button component now looks like a button ❤️

    techletter app screenshot 1549905908783

    Much clearer 👌

    So how'd we do it?

    Nothing special. You might even say "Wait that's it?"

    You take your hooky mess, wrap it in a new method, call it useSomething, and voila: that method is a React hook and you've just created a custom hook. Congratz 👏

    Enjoy your week

    Cheers, ~Swizec

    PS: I discovered the floppotron this morning. It is amazing

    Did you enjoy this article?

    Published on February 11th, 2019 in Front End, Technical

    Learned something new?
    Want to become an expert?

    Here's how it works 👇

    Leave your email and I'll send you thoughtfully written emails every week about React, JavaScript, and your career. Lessons learned over 20 years in the industry working with companies ranging from tiny startups to Fortune5 behemoths.

    Join Swizec's Newsletter

    And get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.

    "Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"

    ~ Ashish Kumar

    Join over 14,000 engineers just like you already improving their careers with my letters, workshops, courses, and talks. ✌️

    Have a burning question that you think I can answer? I don't have all of the answers, but I have some! Hit me up on twitter or book a 30min ama for in-depth help.

    Ready to Stop copy pasting D3 examples and create data visualizations of your own?  Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization

    Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.

    Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created bySwizecwith ❤️