部署在Heroku的Nuxt.js+Express：SPA失效与日志无输出问题求助

Hey there! I’ve dealt with similar headaches when deploying Nuxt.js + Express apps to Heroku, so let me walk you through some fixes and troubleshooting steps that worked for me.

Issue 1: Missing SPA Behavior (Full Page Reloads on Menu Navigation) #

Local runs work fine, but Heroku forces full page reloads? Here’s what to check:

• Verify Nuxt’s Mode & Router Configuration
  First, double-check your nuxt.config.js:

  • If you’re aiming for pure SPA mode, set mode: 'spa' (note that universal mode can also support SPA-like navigation if configured correctly).
  • Ensure router.base matches your app’s URL path—for root domains, it can stay '/', but adjust it if you’re using a subpath.
  • Add the connect-history-api-fallback middleware to your Express server to handle client-side routing. Install it first with npm install connect-history-api-fallback, then add this to your server.js:

    const history = require('connect-history-api-fallback');
    app.use(history());
    // Mount Nuxt's render middleware after the history fallback
    app.use(nuxt.render());
    

• Check Heroku’s Build & Start Scripts
  Make sure your package.json scripts are production-ready:

  "scripts": {
    "dev": "nuxt",
    "build": "nuxt build",
    "start": "node server.js",
    "generate": "nuxt generate"
  }
  

  Heroku runs npm run build during deployment, then npm run start to launch the app. Skipping nuxt build can leave your app in a dev-like state that breaks SPA navigation.

• Confirm Node Environment
  Heroku sets NODE_ENV=production by default, but custom configs might override this. Check with heroku config:get NODE_ENV—if it’s not production, set it with heroku config:set NODE_ENV=production. Nuxt optimizes routing and assets based on this variable.

Issue 2: No Output from heroku logs #

Blank logs are super frustrating—here’s how to dig into it:

• Check if Your Dyno is Running
  Run heroku ps to see if your web dyno is active. If it’s crashed or idle, restart it with heroku restart. A crashed dyno won’t generate logs until it’s up again.

• Verify Your Start Script
  Heroku uses the start script in package.json to launch your app. If the script is missing or points to a non-existent file, the app might fail silently. Double-check that start points to your Express server entry (e.g., node server.js).

• Force Real-Time Logs
  Instead of just heroku logs, try heroku logs --tail to stream logs in real-time. The default log command might miss recent entries, but tailing will catch live output as your app starts or runs.

• Ensure Logs Are Being Emitted
  In your Express and Nuxt code, use standard console.log()/console.error() calls (or a logging library that outputs to stdout/stderr). Heroku only captures logs sent to these streams—if you’re writing to a file or a custom logger that doesn’t pipe to stdout, you won’t see anything in heroku logs.

• Check for Build Errors
  If your app fails during the build phase, Heroku might not show those logs in regular heroku logs output. Run heroku builds:output to see the full build log—this often reveals issues like missing dependencies or build script failures that crash the app before it can generate runtime logs.

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