The simplicity of deploying a static website with GitHub Pages is a process that can be easily transferred to React applications. With just a few steps, it’s easy to host a React app on GitHub Pages for free or build it to deploy on your own custom domain or subdomain.
In this article, we’ll explore how to deploy React apps on GitHub Pages. We’ll also demonstrate how to create a custom domain on GitHub Pages for our static website.
Let’s get started!
Jump ahead:
GitHub Pages is a service from GitHub that enables you to add HTML, JavaScript, and CSS files to a repository and create a hosted static website.
The website can be hosted on GitHub’s github.io
domain (e.g., https://username.github.io/repositoryname
) or on your own custom domain. A React app can be hosted on GitHub Pages in a similar manner.
To deploy your React application to GitHub Pages, follow these steps:
Let’s get started by creating a new React application. For this tutorial, we’ll be using create-react-app
but you can set up the project however you prefer.
Open the terminal on your computer and navigate to your preferred directory. For this tutorial, we’ll set up the project in the desktop directory, like so:
cd desktop
Create a React application using create-react-app
:
npx create-react-app "your-project-name"
In just a few minutes, create-react-app
will have finished setting up a new React application!
Now, let’s navigate into the newly created React app project directory, like so:
cd "your-project-name"
This tutorial is limited to demonstrating how to deploy a React application to GitHub Pages, so we’ll leave the current setup as it is without making any additional changes.
The next step is to create a GitHub repository to store our project’s files and revisions.
In your GitHub account, click the + icon in the top right and follow the prompts to set up a new repository.
After your repository has been successfully created, you should see a page that looks like this:
Awesome! Let’s proceed to the next step.
Now that the GitHub remote repository is set up, the next step is to initialize Git in the project so that we can track changes and keep our local development environment in sync with the remote repository.
Initialize Git with the following command:
git init
Now, we’ll commit our code and push it to our branch on GitHub. To do this, simply copy and paste the code received when you created a new repository (see the above repo screenshot).
git commit -m "first commit" git branch -M main git remote add origin https://github.com/nelsonmic/testxx.git git push -u origin main
Next, we’ll install the gh-pages
package in our project. The package allows us to publish build files into a gh-pages
branch on GitHub, where they can then be hosted.
Install gh-pages
as a dev dependency via npm:
npm install gh-pages --save-dev
Now, let’s configure the package.json
file so that we can point our GitHub repository to the location where our React app will be deployed.
We’ll also need to add predeploy
and deploy
scripts to the package.json
file. The predeploy
script is used to bundle the React application; the deploy
script deploys the bundled file.
In the package.json
file, add a homepage
property that follows this structure: http://{github-username}.github.io/{repo-name}
Now, let’s add the scripts.
In the package.json
file, scroll down to the scripts
property and add the following commands:
"predeploy" : "npm run build", "deploy" : "gh-pages -d build",
Here’s a visual reference:
That’s it! We‘ve finished configuring the package.json
file.
Now, let’s commit our changes and push the code to our remote repository, like so:
git add . git commit -m "setup gh-pages" git push
We can deploy our React application by simply running: npm run deploy
. This will create a bundled version of our React application and push it to a gh-pages
branch in our remote repository on GitHub.
To view our deployed React application, navigate to the Settings tab and click on the Pages menu. You should see a link to the deployed React application.
We can deploy our React app to GitHub’s domain for free, but Github Pages also supports custom subdomains Apex domains. Here are examples showing what each type of subdomain looks like:
Supported custom domain | Example |
www subdomain |
www.logdeploy.com |
Custom subdomain | app.logdeploy.com |
Apex domain | logdeploy.com |
Right now, if we navigate to https://nelsonmic.github.io/logdeploy/ we’ll see our recently published website. But, we could also use a custom subdomain or an Apex domain instead.
Here are the steps to set those up:
CNAME
file at the root of your repositoryCNAME
record on your domain service provider points to the GitHub URL of the deployed website (in the case of this example, nelsonmic.github.io/logdeploy/). To do so, navigate to the DNS management page of the domain service provider and add a CNAME
record that points to username.github.io
where username
is your GitHub usernameTo deploy to an Apex domain, follow the first two steps for deploying to a custom subdomain but substitute the below for the third step:
ALIAS
record or ANAME
record that points your Apex domain to your GitHub Pages IP addresses, as shown:If you’ve previously deployed a React app that uses React Router for routing to Netlify, you’re aware that you need to configure redirects for your URLs. Without redirects, users will get a 404 error when they try to navigate to different parts of your application.
Netlify makes it simple to configure redirects and rewrite rules for your URLs. All you need to do is create a file called _redirects
(without any extensions) in the app’s public folder.
Then simply add the following rewrite rule within the file:
/* /index.html 200
No matter what URL the browser requests, this rewrite rule will deliver the index.html
file instead of returning a 404.
If we want to handle page routing when we deploy to GitHub Pages, we’ll need to do something similar. Let’s configure routing for our previously deployed project.
First, we need to install a router. Start by installing React Router in the project directory, like so:
npm install react-router-dom
Now, follow the below four steps.
Step 1: Connect a HashRouter
to the application to enable client-side routing:
import React from 'react'; import ReactDOM from 'react-dom/client'; import './index.css'; import App from './App'; import reportWebVitals from './reportWebVitals'; import { HashRouter as Router } from "react-router-dom"; const root = ReactDOM.createRoot(document.getElementById('root')); root.render( <Router> <App /> </Router> ); // If you want to start measuring performance in your app, pass a function // to log results (for example, reportWebVitals(console.log)) // or send to an analytics endpoint. Learn more: https://bit.ly/CRA-vitals reportWebVitals();
Our index.js
file should look like the above code block. Since GitHub Pages does not support browser history, we’re employing a HashRouter
. Our existing path does not assist GitHub Pages in determining where to direct the user (since it is a frontend route).
To solve this issue, we must replace our application’s browser router with a HashRouter
. The hash component of the URL is used by this router to keep the UI in sync with the URL.
Step 2: Create the routes:
Create a routes
folder and the required routes. These routes can be configured in the app.js
file. But first, let’s create a Navbar
component that can be visible on all pages.
Step 3: Create a Navbar
component:
>import { Link } from "react-router-dom" const Navbar =()=>{ return ( <div> <Link to="/">Home</Link> <Link to="/about">About</Link> <Link to="/careers">Careers</Link> </div> ) } export default Navbar;
Now we can add the Navbar
component alongside the configured routes in the app.js
file.
Step 4: Set up routes in the app.js
file:
import './App.css'; import { Routes, Route} from "react-router-dom"; import About from "./routes/About"; import Careers from "./routes/Careers"; import Home from "./routes/Home"; import Navbar from './Navbar'; function App() { return ( <> <Navbar /> <Routes> <Route path="/" element={<Home />} /> <Route path="/about" element={<About />} /> <Route path="/careers" element={<Careers />} /> </Routes> </> ); } export default App;
Now that we’re done with the setup, let’s push our code, like so:
>git add . git commit -m "setup gh-pages" git push
Next, we simply deploy and our app should route properly:
>npm run deploy
Once these steps are completed, our deployed application will correctly route the user to any part of the application they desire.
When we configure Netlify deployments, we’re given a preview link to view our deployment before it is merged into the main branch. Let’s create the same for GitHub Pages.
We’ll use a simple tool called Livecycle for this, which saves us the trouble of having to do this using GitHub Actions. Every time we make a pull request in our repository, Livecycle assists us in creating a preview environment.
To create a preview environment, follow these steps:
Select a template based on your project’s tech stack. For our example, we’d select Create React App NPM, since our project was built using create-react-app:
Once deployment is successful, anytime we make a PR or push a commit to that PR we’ll get a preview link.
GitHub Pages is easy to get started with and free to use, making it a very attractive option for developers of all skill levels.
In this article, we demonstrated how to use GitHub Pages to convert a React app into a static website. We showed how to deploy the React app to GitHub’s domain, as well as to a custom subdomain. If you’re looking for an easy way to share your code with the world, GitHub Pages is a great option.
Install LogRocket via npm or script tag. LogRocket.init()
must be called client-side, not
server-side
$ npm i --save logrocket // Code: import LogRocket from 'logrocket'; LogRocket.init('app/id');
// Add to your HTML: <script src="https://cdn.lr-ingest.com/LogRocket.min.js"></script> <script>window.LogRocket && window.LogRocket.init('app/id');</script>
Learn more about the 5 best JavaScript libraries for dealing with multidimensional arrays, such as ndarray, math.js, and NumJs.
We spoke with Dom about his approach to balancing innovation with handling tech debt and to learn how he stays current with technology.
Vite is a versatile, fast, lightweight build tool with an exceptional DX. Let’s explore when and why you should adopt Vite in your projects.
Explore advanced capabilities for content sharing with the navigator.share
API, including dynamic content sharing, custom share targets, and batch sharing.
12 Replies to "Deploying React apps to GitHub Pages"
The deploy script code has an error. There should be a space before -d
Hello Kevin,
We’ve corrected the typo. Thanks for reading LogRocket’s blog!
Thank you for pointing this out.
this didn’t work for me. I’m seeing the html of my index.js file instead of the actual site
Hi Henry, thank you for reading. Can you provide more context to this problem?
“gh-pages-d build”, there is a space in -d. if you would not add space you can get message that “‘gh-pages-d’ is not recognized as an internal or external command,
operable program or batch file. ”
should be like this
“deploy”: “gh-pages -d build”
Hi Fazeelat, thanks for pointing out the typo. We’ve fixed it. Thanks for reading LogRocket’s blog!
Thank you for the artice, very well put together.
Thank you! I’m glad it was a good read.
Thank you for putting everything very well. I could easily go through the steps and got the deploying done. A big thank you
Hi Michael, thank for posting this. I’m getting an error near the beginning.
npm install gh-pages –save-dev
Unsupported engine {
npm WARN EBADENGINE package: ‘@csstools/[email protected]’,
npm WARN EBADENGINE required: { node: ‘^14 || ^16 || >=18’ },
npm WARN EBADENGINE current: { node: ‘v17.9.1’, npm: ‘8.11.0’ }
I think this is connected to problems I’m having using the command line to manage my repository on github… but maybe I fixed that and this is a new problem…?
Also, I’d like to subscribe to your blog, but I’m not sure what logrocket is and how to subscribe without paying a membership fee.
Hey, how come you listed the ‘git branch -M main’ command during setup? How does that affect the process?