在Heroku部署的Node+Express网站中无法在index.js创建新路由

Hey there! Let's break down why your new routes aren't working in your Node.js/Express app deployed on Heroku. Based on the code snippet you shared and common pitfalls with Express + Heroku setups, here are the most likely fixes:

1. Check Your Route Order (Most Common Culprit!) #

Express matches routes in the order they’re defined. If your new route is placed after a static file middleware or a catch-all (*) route, it’ll never get hit. For example:

// ❌ Wrong: New route comes after static/catch-all
app.use(express.static(path.join(__dirname, 'public')));
app.get('*', (req, res) => res.sendFile(path.join(__dirname, 'public', 'index.html')));

// This route will never run!
app.get('/new-route', (req, res) => {
  res.send('Hello from my new route!');
});

// ✅ Correct: Define new routes first
app.get('/new-route', (req, res) => {
  res.send('Hello from my new route!');
});

// Then static files and catch-all
app.use(express.static(path.join(__dirname, 'public')));
app.get('*', (req, res) => res.sendFile(path.join(__dirname, 'public', 'index.html')));

2. Fix Syntax or Logic Errors in the New Route #

Even a tiny syntax mistake (like missing parentheses, unclosed brackets, or an unhandled async operation) can break your route. For example:

• If your route uses async, make sure you handle errors with try/catch or pass errors to next():

  app.get('/new-async-route', async (req, res, next) => {
    try {
      const data = await someAsyncFunction();
      res.json(data);
    } catch (err) {
      next(err); // Let Express handle the error
    }
  });
  

• Double-check that you’re sending a response (res.send(), res.json(), etc.)—if you forget, the request will hang, making it seem like the route doesn’t exist.

3. Clear Heroku’s Deployment Cache #

Heroku sometimes caches dependencies or build artifacts, which can prevent new code from being deployed properly. Fix this by purging the cache and redeploying:

# Install the heroku-repo plugin if you haven't
heroku plugins:install heroku-repo

# Purge the cache
heroku repo:purge_cache -a your-app-name

# Make an empty commit to trigger a fresh deploy
git commit --allow-empty -m "Purge Heroku cache"
git push heroku main

4. Verify Dependencies and Environment Variables #

• If your new route uses a new npm package, make sure you added it to dependencies (not just devDependencies) with npm install --save package-name. Heroku skips devDependencies in production.
• If your route relies on environment variables (like your TW_KEYS), confirm they’re set in Heroku:

  # Check existing env vars
  heroku config -a your-app-name
  
  # Add a missing one if needed
  heroku config:set NEW_VAR=value -a your-app-name
  

5. Check Heroku Logs for Hidden Errors #

The best way to debug is to look at Heroku’s real-time logs—they’ll show you exactly what’s breaking:

heroku logs --tail -a your-app-name

Look for errors like ReferenceError, ModuleNotFoundError, or unhandled promise rejections—these are often the root cause of unresponsive routes.

6. Confirm Your Port Setup #

Ensure your app is listening on the port Heroku provides (not a hardcoded port like 3000):

const PORT = process.env.PORT || 3000;
app.listen(PORT, () => {
  console.log(`Server running on port ${PORT}`);
});

Heroku dynamically assigns ports, so this ensures your app accepts incoming requests.

Walk through these steps one by one—start with route order (it’s the most common issue!) and check logs early. You’ll have that new route working in no time.

内容的提问来源于stack exchange，提问作者Sahand