Hey there, let's troubleshoot why your Express server works smoothly in dev mode but fails to start after packaging with electron-builder. Based on your code, here are the most common fixes to try:

1. Replace cluster with an Electron-friendly server launch method #

The cluster module works great in standard Node.js environments, but it can behave unexpectedly in packaged Electron apps—especially with the default asar packaging enabled. The child process spawned via cluster.fork() might fail to resolve your app.js path correctly, or hit permission restrictions in the packaged context.

Here's a reliable alternative using child_process.spawn (replace your start.js with this):

const { spawn } = require('child_process');

// Launch Express server with full log visibility for debugging
const serverProcess = spawn(process.execPath, [require.resolve('./app.js')], {
  stdio: ['inherit', 'inherit', 'inherit'] // Forward server logs to the console
});

// Catch server launch errors
serverProcess.on('error', (err) => {
  console.error('Server failed to start:', err);
});

// Start the Electron app
require('./main.js');

For even more simplicity, you can start the Express server directly in your main.js right after the app is ready:

// In main.js, inside the app.on('ready') callback
app.on('ready', function(){
  var appWindow;
  appWindow = new browserWindow({ 
    width:1120, 
    height:620, 
    webPreferences: { plugins: true }, 
    icon: path.join(app.getAppPath(), '/public/icon/icon.png') // Fix path here too!
  }); 
  appWindow.loadURL(`file://${app.getAppPath()}/public/prva.html`);

  // Launch your Express server here
  require('./app.js');
});

2. Fix path resolution for packaged apps #

When electron-builder packages your app into an asar archive, __dirname no longer points to your source code directory—it points to the internal path of the asar archive. This breaks any relative paths in app.js (like static files, templates, etc.).

Update all path references in app.js to use app.getAppPath() (from Electron's app module) for absolute, reliable paths:

// In app.js
const express = require('express');
const path = require('path');
const { app: electronApp } = require('electron'); // Import Electron's app module

const app = express();

// Correct path for static files
const staticDir = path.join(electronApp.getAppPath(), 'public');
app.use(express.static(staticDir));

// Correct path for EJS templates (if you use them)
app.set('views', path.join(electronApp.getAppPath(), 'views'));

Don't forget to fix paths in main.js too, like the window icon and loadURL path as shown in the code snippet above.

3. Test with asar packaging disabled (temporary debug step) #

To confirm if asar is causing path-related issues, temporarily disable it in your package.json build config:

"build": {
  "appId": "com.artros.app",
  "productName": "Artros",
  "asar": false, // Disable asar for testing
  "win": {
    "target": "portable",
    "icon": "build/icon.ico"
  },
  "mac": {
    "target": "dmg"
  }
}

If the server starts successfully after this, you know path resolution was the root problem. Stick with the app.getAppPath() fixes and re-enable asar once paths are corrected.

4. Capture server logs to debug hidden errors #

Packaged Electron apps don't show console output by default, so you might miss critical errors that crash your server on startup. Add logging to a file in app.js to capture these details:

// At the top of app.js
const fs = require('fs');
const path = require('path');
const { app: electronApp } = require('electron');

// Log to a file in your app's user data directory
const logFilePath = path.join(electronApp.getPath('userData'), 'server.log');
const logStream = fs.createWriteStream(logFilePath, { flags: 'a' });

// Redirect console logs to the file
console.log = (...args) => {
  const logLine = `${new Date().toISOString()}: ${args.join(' ')}\n`;
  logStream.write(logLine);
  process.stdout.write(logLine);
};

console.error = (...args) => {
  const errorLine = `${new Date().toISOString()} [ERROR]: ${args.join(' ')}\n`;
  logStream.write(errorLine);
  process.stderr.write(errorLine);
};

You can find the userData directory at:

• Windows: C:\Users\<YourName>\AppData\Roaming\Artros
• Mac: ~/Library/Application Support/Artros

Check this log file for any errors that might be preventing your server from starting.

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