Скачать или смотреть Fixing the 404 Error in Your Express and Node.js Application

Learn how to resolve the common `404 error` in Express.js applications with a step-by-step guide and code explanations.
---
This video is based on the question https://stackoverflow.com/q/69307448/ asked by the user 'Cristian Ștefan' ( https://stackoverflow.com/u/14370526/ ) and on the answer https://stackoverflow.com/a/69307951/ provided by the user 'ChaoLong Piao' ( https://stackoverflow.com/u/16988841/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: 404 error on express + nodeJS, on a normal route

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Solving the 404 Error in an Express + Node.js Application

Creating your first web application can be an exciting yet challenging endeavor, especially when running into roadblocks like 404 errors. This article will help demystify this common issue and provide you with a clear path to resolving it in your Express and Node.js application.

Understanding the Problem

You are likely familiar with the feeling of frustration that accompanies receiving a 404 error. In the context of an Express application, this error signifies that the server cannot find the requested path. In your case, when trying to access http://localhost:3000/all, a 404 error indicates that the application does not know how to handle requests for that specific route.

Current Code Structure

To understand why your application is returning a 404 error, let's take a look at your current code setup:

routes/index.js: This file contains the routing logic for your application.

app.js: This is the main application file where the Express app is configured and routes are defined.

Here's what you currently have in your code:

[[See Video to Reveal this Text or Code Snippet]]

In this snippet from app.js, you're only mounting the indexRouter.

[[See Video to Reveal this Text or Code Snippet]]

Breaking Down the Solution

To resolve the 404 error, you need to ensure that Express correctly recognizes and routes requests to the /all path. Here’s how to do that:

Step 1: Create a New Route File

Create a new file named all.js in the routes directory.

Insert the following code into routes/all.js:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Update the Main Application File

Next, you need to update your app.js so that it knows about the new route.

Modify your app.js to include the new route:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Testing Your Application

Restart your Express server for changes to take effect.

Access http://localhost:3000/all in your web browser again.

You should now see the all_hotels page instead of a 404 error message.

Conclusion

By restructuring your route handling and properly mounting the allRouter, you have successfully resolved the 404 error. If you continue to learn and build with Express and Node.js, keeping a keen eye on your routes and how they are configured plays a significant role in your application's success. Happy coding!