106 reads

Stop using custom templates in your Webpack React apps

by Colby FayockJuly 9th, 2018

Too Long; Didn't Read

<a href="https://hackernoon.com/tagged/google" target="_blank">Google</a> “webpack react” and you’ll notice the guides in the top results all have one thing in common: they create custom HTML templates for their React applications.

Companies Mentioned

featured image - Stop using custom templates in your Webpack React apps

Google “webpack react” and you’ll notice the guides in the top results all have one thing in common: they create custom HTML templates for their React applications.

See, React apps need a root node that serves as a mounting point when rendering to the DOM, so most times you’ll simply see a <div> with an ID of root inside a basic HTML page with not much else in the file.

// main.js

ReactDOM.render(<h1>Hai!</h1>, document.getElementById('root'));

// index.html

...nothing unique...<div id=”root”></div>...nothing unique...

Why is that bad?

Well, bad is a strong word… Creating that template might seem necessary to get the app started, but while doing that, you’re overwriting some of the default functionality HTML Webpack Plugin provides, such as setting up essential meta tags like charset without needing to maintain them yourself and generating the application HTML on the fly.

There’s a better way!

Partials for HTML Webpack Plugin is an extension for HTML Webpack Plugin that provides HTML partial support out of the box. Simply set up your HTML file with only the snippet you need, toss the path in your Webpack configuration, and you’re done!

Less of:

// index.html

...cookiecutter...<script async src="...googletagmanager.com/gtag/js..."></script>...cookiecutter...<div id=”root”></div>...cookiecutter...

And more of:

// partials/body.html

// partials/analytics.html

// path/to/output.html

<!DOCTYPE html><html><head><meta charset="UTF-8"><script async src="...googletagmanager.com/gtag/js..."></script><title>Webpack App</title></head><body><div id="root"></div><script type="text/javascript" src="main.js"></script></body></html>

This removes the need to create your standard index.html and let’s Webpack do all of the work for you now and in the future.

How does one add these partials?

This assumes you already have a basic React app set up. For more info on getting a React Webpack app spun up from scratch, try one of those top results on Google.

Let’s get to it! We’ll start by adding our dependency:

yarn add html-webpack-partials-plugin -D

npm add html-webpack-partials-plugin --save-dev

Create your partial:

// path/to/partials/body.html

Require your newly installed dependency at the top of your Webpack config:

// webpack.config.js

const HtmlWebpackPartialsPlugin = require(‘html-webpack-partials-plugin’);

Add the partial config anywhere after HTML Webpack Plugin in the plugins list:

// webpack.config.js

new HtmlWebpackPlugin(),new HtmlWebpackPartialsPlugin({path: ‘./path/to/partials/body.html’})

If you have an HTML file already set up in your configuration, nows the time to remove it. For now, just comment it out so we can easily reference it later.

// webpack.config.js

plugins: [..new HtmlWebPackPlugin({// template: “./path/to/index.html”,// filename: “index.html”}),...]

Assuming you don’t have anything else critical in your index.html file, you should now be able to run your Webpack build script and you’re done!

What about the other stuff in my template?

You’re in luck, you can set up as many partials as you’d like to manage the rest of the code.

Let’s say you have an analytics script that you critically need to add directly to the page:

// path/to/index.html

<!DOCTYPE html><html><head>

<title>My Awesome App</title>

</head><body><div id=”root”></div></body></html>

First, create a partial, similar to the React root file we created:

// /path/to/partials/analytics.html

Set it up in your config:

// webpack.config.js

new HtmlWebpackPartialsPlugin([{path: ‘./path/to/partials/body.html’},{path: ‘./path/to/partials/analytics.html’,priority: ‘high’,location: ‘head’})

Run your Webpack build script and you’re done!

Notice we updated the single object to an array of objects. Both ways will work.

And the rest of index.html…

Any of the other HTML snippets in your custom template, you can follow the same pattern as the above. Once you’re all done and feel confident you have all of the critical elements migrated, you can remove that file and take out those 2 commented lines out of your Webpack config.

If you’re not confident, make a backup! Don’t make an assumption and lose your work.