Skip to main content

Delicious Reverie

blog of developer & bookworm benjamin read

Dynamic client side routes in GatsbyJS

Would you use GatsbyJS for a dynamic app? Yes I would. The reason is that I can make good use of Gatsby's great developer experience, as well as do everything I would normally do in a React application. Here's how I recently implemented dynamic routing.

Disclaimer: My colleage Romina Moya originally discovered how Gatsby could do this, and showed it to me afterwards.

I've been learning more about Amazon Web Services recently, and found an excellent tutorial written by the makers of Seed, a sort of CI pipeline for serverless applications. You can find the tutorial at

I wanted to diverge from the tutorial a little on the frontend, especially since I really enjoy working with GatsbyJS and wanted to use it's static rendering where I could.

One of the lessons uses React Router to render routes for notes like this:


where the last part of the url (the "pathname") needs to be generated client-side only. The reason is that the component would resolve to any number of records in the database, and needs be accessible only to the logged-in user.

To achieve this in Gatsby I referred to their excellent documentation (, but there's a lot of information in that documentation, and it can be a little difficult to see what you need to do. So here's some extra pointers that I thought might be useful:


In my applications as in most Gatsby sites, I use a wrapping component that I name "layout" or "entry". If you don't have that, you could effectively do the same thing by adding a file in the root of your project named "gatsby-browser.js" and using the onClientEntry() api (

In that file I needed to first import { Router } from "@reach-router", and also import { navigate } from "gatsby" then in the render function add this:

  <BounceToHome default />

The BounceToHome function is for any path the router comes across that isn't defined (as you can see from the default prop I passed to it). This is useful for if the user types anything That function uses navigate() that I imported earlier:

const BounceToHome = () => {
  useEffect(() => {
    navigate("/", { replace: true });
  }, []);
  return null;

As you can see I use the useEffect hook to navigate the user home on the first render.

Rendering client-only component

At the top of the file I've imported the functionality I already defined for rendering, editing and deleting notes:

import Notes from "./Notes";

Now as a child of the Router component I'm going to add in my Notes component:

<Notes path="/notes/:noteId/" component={Notes} />

The path tells Reach Router that I want to accept paths with a prefix "/notes", and the colon after that is a variable that will be passed to your component. It could be called anything you like, I thought noteId was the most relevant name for what I was building.

On the following line I've passed to the router which component I want to render on that path.

Now I can use that component in the page in this way:

export default function Notes({noteId}) {
  useEffect(() => {
    function loadNote() {
      return get("notes", `/notes/${noteId}`, '');
    async function onLoad() {
      try {
        const note = await loadNote();
      } catch (error) {
  }, [noteId]);

Whenever the noteId changes the useEffect hook runs and loadNote() gets the note using functionality available in the aws-amplify package.

Gatsby is ready for Apps!

If React is "just JavaScript", then Gatsby is "just a javascript framework", with all of the benefits that brings you, as well as some significant other things like better accessibility, static rendering, and loads of other cool stuff.

Let's not be too quick to pigeon-hole Gatsby into a certain corner: it's a versatile set of tools that allows us to jump start our projects and create any number of really cool things.

Update: don't put this in your Layout / Entry file!

After playing with this a little more, I realised that client only routes override file routes ... so if you have the dynamic routing on the root path (usually "/"), it'll override everything else and you won't be able to navigate to any other page you have defined in the pages folder.

So it's best to scope your client routes to a folder (such as app), and avoid overriding your other pages!

You're currently on the javascript disabled version of the site. To enable the site search and some pretty animations, view the javascript enabled react app.

About This Site

Delicious Reverie is the blog of developer & bookworm benjamin read. Set in Skybird and your system font. Built with Gatsby, hosted by Netlify. © Some rights are reserved. This site doesn't use any cookies or other session storage and has no tracking scripts.

Where you can find me: