Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Seamlessly Render a Preact Component in a React Project [Livecoding]

DZone's Guide to

Seamlessly Render a Preact Component in a React Project [Livecoding]

Have you ever wanted to render a Preact component inside a React project? It's hard, right? Read on to find out how to get it to work.

· Web Dev Zone ·
Free Resource

Deploying code to production can be filled with uncertainty. Reduce the risks, and deploy earlier and more often. Download this free guide to learn more. Brought to you in partnership with Rollbar.

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.

Set your pragma to `h` and conditionally assign h within the scope you want:

/** @jsx h */
import React from 'react'
import { h } from 'preact'

const WithReact = () => {
let h = React.createElement;
return <div>react</div>
}

const WithPreact = () => (
<div>preact</div>
)

- Jason Miller (@_developit) February 26, 2018

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

Deploying code to production can be filled with uncertainty. Reduce the risks, and deploy earlier and more often. Download this free guide to learn more. Brought to you in partnership with Rollbar.

Topics:
web dev ,react ,preact

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}