Remix pathless layout routes

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

Now that we know how to make shared layouts in Remix, there might be times when you want a shared layout but not the shared routes.
For instance, what happens when we want to introduce multiple auth routes that share one layout?
We might go for an auth folder and inside create files like: login.tsx and register.tsx.
That would work, right? And the answer is yes.
But the downside of that approach is that we get all the URLs prefixed with /auth:
http://mywebsite.com/auth/login
http://mywebsite.com/auth/register
Remix came up with pathless layout routes for this problem.
The main idea behind these pathless layout routes is that they can share a layout but are not read as URL segments.
To use them, you have to prefix the folder with two underscores: __auth.
And for the layout file goes the same, prefix it with __auth.tsx.
Let's try and set up these login pages to see it in action.
First, create the __auth folder inside your routes directory.
Then go ahead and create the layout file, which will hold our main auth layout.
This file is called __auth.tsx and is located at the root of the routes directory.
First, remove any existing login or register routes and create login.tsx and register.tsx inside the __auth directory.
Each one can have a file similar to this:
export default function Login() {
return <p>This is the login page</p>;
}
Note: Make sure to rename the function name and the actual copy.
If we now run the website, we can navigate to /login and /register, and our auth layout will still be there!

Pretty cool stuff, Remix!
You can also find the completed code on GitHub.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter