Have you ever wanted to render a Preact component inside a React project?
It's hard, right? First of all, why? Because. Second of all, how do you reconcile the two different implementations of JSX?
Preact and React are pretty similar, you see. Both are based on components, both leverage JSX to make your life easier, and for the most part, they look interchangeable.
// React componentimport React from 'react';const Header => <h1>I am a header</h1>
// Preact componentimport Preact from 'preact';const Header => <h1>I am a header</h1>
Where they differ greatly is what that
<h1>I am a header</h1> compiles to. For React, it's a
createElement() call. For Preact ,it's a
And that's where the trouble begins.
I got this idea from Jason himself.
Here's how it looks in code 👇
There are 4 parts to this:
- Tell Babel to use
hfor the JSX function. That's the
/** @jsx h */magic comment at the top.
- Import both React and Preact. You'll need both.
- Make a Preact component. Or take one from somewhere else. It doesn't matter. Whatever you want :)
- Create a
<Wrapper />React component
<Wrapper /> component is where the magic happens.
render() method sets
React.createElement and outputs an anchor div. Setting
h ensures that this part of JSX compiles into React's
createElement calls. This makes the component integrate seamlessly with the rest of your project.
Then we hook into the component lifecycle with
componentDidUpdate. We call
renderPreact in both of them to ensure our wrapper component always ends up rendering Preact.
Same as my React D3 blackbox approach for quickly wrapping D3 code in React components.
renderPreact, we then use Preact's
render() function to render the Preact component into our anchor div. This works the same way as Preact's normal DOM rendering where you call
render(<App />, document.getElementById('root')) to put your app into a root div.
The JSX compiles into Preact's
h() calls because we didn't mess with the setting, and React refs give us a direct reference to the anchor DOM node.
You can now compare React and Preact side-by-side in my interactive DOM benchmark. I think it's a fair comparison because Preact handles its own internals.
Numbers are kinda high though. Preact is supposed to be faster than React because it's closer to the metal. I wonder if it's running in dev mode 🤔
Here's how it works 👇
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. 👌"
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
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️