A route is a section of Express code that associates an HTTP verb ( GET , POST , PUT , DELETE , etc.), a URL path/pattern, and a function ( route handler callback ) that is called to handle that pattern.
The path is the part of a request URL after the hostname and port number, so in a request to localhost:3000/about, the path is /about (in this example, the hostname is localhost, the port number is 3000).
The HTTP verb is always included in the request.
\nGET requests are used for retrieving resources from a server.
POST is the HTTP method verb used for creating new resources.
PUT requests are used for updating existing resources.
DELETE requests are used for deleting existing resources.
Express routes usually take two arguments, a path (usually a string), and a callback function to handle the request and send a response.
\napp.get("/about", () => {\n res.send("Hello from Express")\n})The route above will match any GET request to /about and call the callback function, passing in two objects as the first two arguments.
These objects represent the request sent to the server and the response that the Express server should eventually send to the client.
\nExpress servers send responses using the .send() method on the response object. send will take any input and include it in the response body.
If no routes are matched on a client request, the Express server will handle sending a 404 Not Found response to the client.
\nExpress allows us to set the status code on responses before they are sent. Response codes provide information to clients about how their requests were handled.
\nUntil now, we have been allowing the Express server to set status codes for us. For example, any res.send() has by default a 200 OK status code.
The res object has a .status() method to allow us to set the status code, and other methods like .send() can be chained from it.
app.get("/about", () => {\n res.status(200).send("Hello from Express")\n})Express tries to match requests by route, meaning that if we send a request to /api-endpoint.
Express searches through routes in the order that they are registered in your code. The first one that is matched will be used, and its callback will be called.
\nIf there are no matching routes registered, or the Express server has not sent a response at the end of all matched routes, it will automatically send back a 404 Not Found response, meaning that no routes were matched or no response was ultimately sent by the registered routes.
\nWe can create dynamic path segments (called parameters) by adding a : to Express router definitions.
Express parses any parameters, extracts their actual values, and attaches them as an object to the request object: req.params. The name you add after : is the name of the key by which you can extract data from req.params.
const mobiles = { apple: { price: 1000 }, samsung: { price: 600 } }\n\n//GET/mobiles/apple\napp.get("/mobiles/:brand", (req, res, next) => {\n console.log(req.params) // => {brand: 'Apple'}\n res.send(mobiles[req.params.brand])\n})In the code snippet above, a .get() route is defined to match /mobiles/:brand path.
When a GET request arrives for /mobiles/apple, the callback is called.
Inside the callback, req.params is an object with the key brand and the value apple, which was present in the actual request path. The appropriate mobile brand is retrieved from the mobiles object and sent back to the client.
Query strings appear at the end of the path in URLs, and they are indicated with a ? character. For example, in /persons/1?name=Morgan&age=26, the query string is name=Morgan&age=26 and the path is /persons/1/.
Query strings do not count as part of the route path. Instead, the Express server parses them into a JavaScript object and attaches it to the request body as the value of req.query.
The key: value relationship is indicated by the = character in a query string, and key-value pairs are separated by &.
In the above example route, the req.query object would be { name: 'Morgan', age: '26' }.
const persons = { 1: { name: "Charles", age: "25" } }\n\n// PUT /persons/1?name=Morgan&age=26\napp.put("/persons/:id", (req, res, next) => {\n const personUpdates = req.query\n persons[req.params.id] = personUpdates\n res.send(persons[req.params.id])\n})Here, we have a route for updating persons by ID. When a PUT /persons/1?name=Morgan&age=26 request arrives, our callback function is called and, we create a personUpdates variable to store req.query. Since req.params.id is '1', we replace persons['1']‘s value with personUpdates. Finally, Express sends back the new persons['1'].
When updating, many servers will send back the updated resource after the updates are applied so that the client has the exact same version of the resource as the server and database.
\nWe use express.Router to create modular, mountable route handlers.
To create an instance of the Express Router, invoke the .Router method on the top-level Express import. A route instance is a complete middleware and routing system.
To use a router, we mount it at a certain path using app.use() and pass in the router as the second argument.
const express = require("express")\n\nconst router = express.Router()\n\nrouter.get("/", (req, res, next) => {\n res.send("Hello from Express")\n})\n\nrouter.get("/about", (req, res, next) => {\n res.send("Express is a Node.js application framework.")\n})\n\nmodule.exports = routerconst express = require('express');\n\nconst expressRoutes = require('./routes/expressRoutes');\n\nconst app = express();\n\napp.use(expressRoutes);\n\nconst PORT = 5000 || process.env.PORT;\n\napp.listen(5000, () => {\n console.log(`The server is listening on port ${PORT}`);\n});