What's up, I'm glad you're here! We'll be discussing how to set up and structure external routes for our Node.js server by usingExpress’ routers. External routes can be a great way to keep your code organized, maintainable, and easy to understand; they help create a structure that is easy to examine in order to locate a particular piece related to your work. If you haven't set up a Node.js server before, make sure to givethis tutorial a look, it goes into detailed instruction on how to set up a Node.js server with Express.
You can find the video tutorialhere, and the code onGitHub.

What Do You Mean?

Okay, so what do I mean by external routes? Well, as you get more and more routes set up inside of your server, things can get a bit clunky and confusing. External routing is a way of structuring your code so that it stays nice and organized by taking the route implementations outside of the main server file and moving them into a separate router file.

Can I Get An Example?

Of course. Let's say that we have a simple server file with a bunch of routes,index.js:

varexpress=require('express');varapp=express();// Our first routeapp.get('/',function(req,res){res.send('Hello Index!');});// Our A routeapp.get('/A',function(req,res){res.send('Hello A!');});// Our B routeapp.get('/B',function(req,res){res.send('Hello B!');});// Our C routeapp.get('/C',function(req,res){res.send('Hello C!');});// Listen to port 5000app.listen(5000,function(){console.log('Dev app listening on port 5000!');});

We can see that adding more routes and functionality would easily make this file very confusing and hard to maintain. It may not be doing a whole lot right now, but imagine developing with it for weeks... months... years. We could start to add routes that handle things such as social media verification, APIs, and even just static pages. So, we want to start separating and structuring our code as our routes can become more niche, and before the index file starts gaining more functionality - it may need to handle more than just routing in the future (and it would if this was a probable application).

The Goal

Our goal is to keep our index clean and our code organized. This is the overview of our file/folder structure, and how we want to separate these route definitions from the main index file. So go ahead and recreate this structure by creating a file calledindex.js and a folder calledroutes with a file calledexternalRoutes.js inside of it:

.├── index.js              └── routes                └── externalRoutes.js

Defining the Router

Now it's time to clean up our index file (the file used in theCan I Get An Example? section). Let's replace all of those routes with a router definition. This router definition will tell the index file where to look for routes to be defined. In this case, we are telling the index (which is at the top-level directory) to search inside of a folder calledroutes for a file calledexternalRoutes.js which contains the external routing implementation (well, not yet... but it will). Inside ofindex.js, let's add:

// Our external routevarexternalRoutes=require('./routes/externalRoutes');app.use('/externalRoutes',externalRoutes);

The entireindex.js file will look like this:

// index.jsvarexpress=require('express');varapp=express();// Our external routevarexternalRoutes=require('./routes/externalRoutes');app.use('/externalRoutes',externalRoutes);// Listen to port 5000app.listen(5000,function(){console.log('Dev app listening on port 5000!');});

Now that's a whole lot cleaner already, isn't it? :)

Implementing the Router

But where did those routes go?! Don't worry! We're going to store them inside of ourexternalRoutes.js. We will create a module export, which will export the definition of our externalRoutes variable. First, create amodule.exports function inside ofexternalRoutes.js, like so:

module.exports=(function(){'use strict';})();

Now add the variable to themodule.exports body that we want to be exported, let's call itexternalRoutes:

module.exports=(function(){'use strict';varexternalRoutes=require('express').Router();returnexternalRoutes;})();

Finally, add the routes to themodule.exports that we've all been waiting for, and you've got yourself some external routes! The entire body ofexternalRoutes.js looks like this:

module.exports=(function(){'use strict';varexternalRoutes=require('express').Router();externalRoutes.get('/',function(req,res){res.send('Hello ExternalRoutes!');});externalRoutes.get('/someRoute',function(req,res){res.send('Hello SomeRoute!');});returnexternalRoutes;})();

External Routes on the Browser

Now that we've got your external routes set up, fire up that server and web browser (for those that aren't sure how, run the commandnode index.js from the top-level directory). Head on over to addresshttp://localhost:5000/externalRoutes, andhttp://localhost:5000/externalRoutes/someRoute to see your routes in action with responses!

Review

Congratulations! You've now successfully set up external routes on your Node.js server. You did this by removing the routes from your index file and structuring your architecture in a way that allows the routes to be a part of an external file. This made your code more maintainable as you start to build your server and add its functionality. If you'd like to learn about deployment, check outAuto-Deploy a Node.js Server: Heroku + GitHub.