javascript - Why does my node.js express code not call console.log()? - Stack Overflow

admin管理员组

文章数量:1340360

How e "homepage requested" never gets output to the terminal console when I run server.js and go to localhost:8000? index.html renders fine

server.js

var express = require("express");
var path = require('path');
var index = require('./routes/index');

var app = express();

var port = 8000;
app.set("views", path.join(__dirname, 'views'));
app.set("view engine", "ejs");
app.engine("html", require("ejs").renderFile);

app.use(express.static(path.join(__dirname, 'client')));

app.use('/', index);

app.listen(port, function() {
  console.log("server started on port", port);
});

index.js

var express = require('express');
var router = express.Router();

router.get('/', function(req, res, next) {
  console.log('homepage requested'); // never executes
  res.render('index.html');          // always executes
});

module.exports = router;

How e "homepage requested" never gets output to the terminal console when I run server.js and go to localhost:8000? index.html renders fine

server.js

var express = require("express");
var path = require('path');
var index = require('./routes/index');

var app = express();

var port = 8000;
app.set("views", path.join(__dirname, 'views'));
app.set("view engine", "ejs");
app.engine("html", require("ejs").renderFile);

app.use(express.static(path.join(__dirname, 'client')));

app.use('/', index);

app.listen(port, function() {
  console.log("server started on port", port);
});

index.js

var express = require('express');
var router = express.Router();

router.get('/', function(req, res, next) {
  console.log('homepage requested'); // never executes
  res.render('index.html');          // always executes
});

module.exports = router;

• javascript
• node.js
• express

Share Improve this question Follow edited Dec 26, 2019 at 7:21 Savan Padaliya 87211 gold badge1313 silver badges2323 bronze badges asked Feb 3, 2017 at 6:45 wannabewannabe 13111 gold badge22 silver badges88 bronze badges 10

• 1 the console log into node , goes to the terminal, not to the navigatot. Could be this? – Álvaro Touzón Commented Feb 3, 2017 at 6:46
• 1 it doesn't print in the terminal – wannabe Commented Feb 3, 2017 at 6:48
• Do you get the "server started on port 8000" line on the terminal? – Bergi Commented Feb 3, 2017 at 6:50
• Yes, that shows up – wannabe Commented Feb 3, 2017 at 6:51
• 1 How are you starting your application? – Kevin B Commented Aug 3, 2018 at 21:33

 |  Show 5 more ments

5 Answers 5

Sorted by: Reset to default 4

console.log('homepage requested') will print the message in the terminal, not in the browser. If you run your server with mand line node index, and then open your page, in the terminal you will see the message.

It has to do with the way you use app.use(express.static(path.join(__dirname, 'client')));

If you take it out you should be able to see the console.log

It appears that if no mount path in the app.use and it sees a route with "/" (home route) it just serves up the static file from the express.static. It doesn't continue with any consoles.

A possible workaround for getting the console.log is to do a URL check in the app.use and that will only print out the home page.

app.use("/", (req, res, next) => {
    if (req.url == "/") {
        console.log("just hompage")

    }
    return next()


}, express.static(path.join(__dirname, "client/build")))

I think part of the reason why this is happening is that express.static ends the response. and you can't console anything after that. I think you don't even need the app.get("/") or router.get("/") because it by default if there is no mount path it work on "/" route. So it sends file automatically.

I think express.static runs on every route hit to check for static files.

In my case, I found that it was writing my console log, but then generating a lot of other messages afterwards, so I had to scroll the terminal back. At first I thought it meant the server was restarting after a file save or crash, so I didn't bother to scroll back, which is why I started searching online. This is different from the way it behaved for me in the past, where my logs were closer to the end.

You have an index file with the same name as the route.

Where you add the route, app.use('/', index);

This won't get called if the index.html file exists and is already served up (as the file has the same name as the route).

Change the name of index.html to index2.html. Then do this

var express = require('express');
var router = express.Router();

router.get('/', function(req, res, next) {
    console.log('homepage requested'); // never executes
    res.render('index2.html');          // always executes
 });

module.exports = router;

Your console should now show your message.

express won't output console.log to the terminal unless you set the DEBUG environment variable to express:* https://expressjs./en/guide/debugging.html

本文标签： javascriptWhy does my nodejs express code not call consolelog()Stack Overflow