Vue项目启动失败求助：桌面端无法运行npm run serve

Hey Mustafa, sorry to hear your Vue project won't start on your desktop even though it runs perfectly on your laptop. Let's walk through some targeted fixes to get it up and running:

1. Align Dependency Versions & Do a Clean Install #

Mismatched or corrupted dependencies are a common culprit here. Since your laptop works, let's sync your desktop setup to match it:

• Delete the node_modules folder, package-lock.json (and yarn.lock if you use Yarn) from your desktop project directory.
• Run npm install to do a fresh install—this ensures you're getting the exact dependency versions that work on your laptop.
• Double-check that your desktop has the same Node.js and npm versions as your laptop. Your desktop is running Node v12.16.1 and npm 6.13.4—verify your laptop matches this. If not, use a version manager like nvm-windows to sync the versions seamlessly.

2. Get Detailed Error Logs #

The current log only shows an exit code 1 without specific details. To uncover the root cause:

• Modify your package.json's serve script to include verbose logging:

  "serve": "vue-cli-service serve --open --verbose"
  

• Run npm run serve again. The --verbose flag will output detailed logs that point to exactly what's failing—whether it's a missing dependency, config error, or port conflict.

3. Check for Port Conflicts #

The default Vue dev server uses port 8080, which might be occupied by another program on your desktop (like XAMPP's Apache). Try:

• Starting the server on a different port:

  npm run serve -- --port 8081
  

• If this works, you'll know port 8080 was the issue—you can either stop the conflicting service or configure Vue to use a different port permanently in vue.config.js.

4. Verify Directory Permissions & Location #

Your project is stored in C:\xampp\htdocs\GitHub\stageFinder—XAMPP directories sometimes have strict permissions that block npm operations. Try:

• Moving the project to a user-owned directory like C:\Users\Mustafa Bolat\Documents\stageFinder.
• Running your command prompt as Administrator before executing npm run serve—this ensures npm has full write access to the project files.

5. Sync Vue CLI Versions #

Mismatched global Vue CLI versions between your laptop and desktop can cause compatibility issues:

• On both machines, run vue --version to check the global CLI version.
• If they differ, uninstall the desktop's current CLI and install the same version as your laptop:

  npm uninstall -g @vue/cli
  npm install -g @vue/cli@[YOUR_LAPTOP_VERSION]
  

Your Error Log for Reference #

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'serve'
1 verbose cli ]
2 info using npm@6.13.4
3 info using node@v12.16.1
4 verbose run-script [ 'preserve', 'serve', 'postserve' ]
5 info lifecycle vuefire@0.1.0~preserve: vuefire@0.1.0
6 info lifecycle vuefire@0.1.0~serve: vuefire@0.1.0
7 verbose lifecycle vuefire@0.1.0~serve: unsafe-perm in lifecycle true
8 verbose lifecycle vuefire@0.1.0~serve: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\xampp\htdocs\GitHub\stageFinder\node_modules\.bin;C:\Program Files (x86)\Razer Chroma SDK\bin;C:\Program Files\Razer Chroma SDK\bin;C:\Program Files (x86)\Razer\ChromaBroadcast\bin;C:\Program Files\Razer\ChromaBroadcast\bin;C:\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps;C:\Users\Mustafa Bolat\AppData\Local\GitHubDesktop\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\Users\Mustafa Bolat\AppData\Local\Programs\Python\Python37-32\Scripts\;C:\Users\Mustafa Bolat\AppData\Local\Programs\Python\Python37-32\;C:\Users\Mustafa Bolat\AppData\Local\GitHubDesktop\bin;C:\Users\Mustafa Bolat\AppData\Local\Programs\Microsoft VS Code\bin;C:\flutter\bin;"C:\Program Files\Git\bin;C:\Program Files\Git\cmd;C:\Windows\System32;";C:\Users\Mustafa Bolat\AppData\Roaming\npm
9 verbose lifecycle vuefire@0.1.0~serve: CWD: C:\xampp\htdocs\GitHub\stageFinder
10 silly lifecycle vuefire@0.1.0~serve: Args: [ '/d /s /c', 'vue-cli-service serve --open' ]
11 silly lifecycle vuefire@0.1.0~serve: Returned: code: 1 signal: null
12 info lifecycle vuefire@0.1.0~serve: Failed to exec serve script
13 verbose stack Error: vuefire@0.1.0 serve: `vue-cli-service serve --open`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:311:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:311:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid vuefire@0.1.0
15 verbose cwd C:\xampp\htdocs\GitHub\stageFinder
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "serve"
18 verbose node v12.16.1
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error vuefire@0.1.0 serve: `vue-cli-service serve --open`
22 error Exit status 1
23 error Failed at the vuefire@0.1.0 serve script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

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