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 component
import React from 'react';
const Header => <h1>I am a header</h1>
// Preact component
import 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 h() call.

And that’s where the trouble begins.

Reconciling createElement() and h()

I got this idea from Jason himself.

Here’s how it looks in code πŸ‘‡

There are 4 parts to this:

  1. Tell Babel to use h for the JSX function. That’s the /** @jsx h */ magic comment at the top.
  2. Import both React and Preact. You’ll need both.
  3. Make a Preact component. Or take one from somewhere else. It doesn’t matter. Whatever you want πŸ™‚
  4. Create a <Wrapper /> React component

That <Wrapper /> component is where the magic happens.

The render() method sets h to 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 componentDidMount and 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.

In 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.

πŸ‘Œ

The benchmark

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 πŸ€”

Learned something new? Want to become a better engineer? πŸ’Œ

Join 9,400+ people just like you already improving their skills.

Here's how it works πŸ‘‡

Leave your email and I'll send you an Interactive Modern JavaScript Cheatsheet πŸ“– right away. After that you'll get a thoughtfully written email every week aboutΒ React, JavaScript,Β  andΒ lessons learned in my 20 years of writing code for companies ranging from tiny startups to Fortune5 behemoths.



Man, I love your way of writing these newsletters. Often very relatable and funny perspectives about the mundane struggles of a dev. Lightens up my day. ~ Kostas

PS: You should also follow me on twitter πŸ‘‰ here.
It's where I go to shoot the shit about programming.