We Keep Coding

Why when I make a change in the Js file the local server stopped when it's running?

Why when I run npm run dev and make any changes in the Js file the local server stopped when it's running and that's happened for windows os only I tried that for Linux and works fine.
it gives me the next error :
C:\Users\osama\OneDrive\Desktop\calculator workflow\scripts\development.js:66
if (err) throw err;
^
[Error: EPERM: operation not permitted, copyfile 'C:\Users\osama\OneDrive\Desktop\calculator workflow\src\scripts\main.js' -> 'C:\Users\osama\OneDrive\Desktop\calculator workflow\.tmp'] {
errno: -4048,
code: 'EPERM',
syscall: 'copyfile',
path: 'C:\\Users\\osama\\OneDrive\\Desktop\\calculator workflow\\src\\scripts\\main.js',
dest: 'C:\\Users\\osama\\OneDrive\\Desktop\\calculator workflow\\.tmp'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # dev: `node ./scripts/task-runner/tasks.js serve`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\osama\AppData\Roaming\npm-cache\_logs\2021-11-23T16_47_01_115Z-debug.log
and this is the log file :
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:\\Users\\osama\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dev'
1 verbose cli ]
2 info using npm#6.14.11
3 info using node#v14.16.1
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle #~predev: #
6 info lifecycle #~dev: #
7 verbose lifecycle #~dev: unsafe-perm in lifecycle true
8 verbose lifecycle #~dev: PATH: C:\Users\osama\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\osama\OneDrive\Desktop\calculator workflow\node_modules\.bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\osama\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files\Git\cmd;C:\Program Files\dotnet;C:\Program Files (x86)\dotnet;C:\Program Files\nodejs;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;%SYSTEMROOT%\System32\OpenSSH;C:\Users\osama\AppData\Local\Microsoft\WindowsApps;C:\Users\osama\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\osama\AppData\Local\hyper\app-3.0.2\resources\bin;C:\Users\osama\AppData\Roaming\npm
9 verbose lifecycle #~dev: CWD: C:\Users\osama\OneDrive\Desktop\calculator workflow
10 silly lifecycle #~dev: Args: [ '/d /s /c', 'node ./scripts/task-runner/tasks.js serve' ]
11 silly lifecycle #~dev: Returned: code: 1 signal: null
12 info lifecycle #~dev: Failed to exec dev script
13 verbose stack Error: # dev: `node ./scripts/task-runner/tasks.js serve`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\osama\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\osama\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid #
15 verbose cwd C:\Users\osama\OneDrive\Desktop\calculator workflow
16 verbose Windows_NT 10.0.22000
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\osama\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
18 verbose node v14.16.1
19 verbose npm v6.14.11
20 error code ELIFECYCLE
21 error errno 1
22 error # dev: `node ./scripts/task-runner/tasks.js serve`
22 error Exit status 1
23 error Failed at the # dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I didn't understand why this happen in windows only and works fine for Linux with track changes and the server never stopped.

'node' is not recognized as an internal or external command, operable program or batch file

I'm running "npm install node-sass" from git-bash-cli in Windows 10 and getting a "'node' is not recognized as an internal or external command,
operable program or batch file." error.
I have been using this setup for years and the issues started when I upgraded node to 10.16.0
To prevent unnecessary replies:
All the questions I have seen simply say to add the path variable.
I have added Node to the PATH variable and tried a number of different ways of writing it. I ended up reinstalling Node.js and that does it automatically, so I just left it as that.
node runs from the command line, just not from scripts, like scripts in the package.json file.
I have tried reinstalling node 8.11.3, which is the version I was using before the problems started, but I get the same error. I am back to v 10.16.0 again.
Error code is as follows:
> node-sass#4.12.0 install C:\projects\true\true\website\truevue\node_modules\node-sass
> node scripts/install.js
'node' is not recognized as an internal or external command,
operable program or batch file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.0.7 (node_modules\#nuxt\builder\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.7 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass#4.12.0 install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#4.12.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Peter\AppData\Roaming\npm-cache\_logs\2019-07-24T23_41_06_896Z-debug.log
Here's the log when I run npm run dev on a Vue project I'm working on
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\Peter\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dev' ]
2 info using npm#6.10.2-next.1
3 info using node#v10.16.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle thisistrue.co#1.0.0~predev: thisistrue.co#1.0.0
6 info lifecycle thisistrue.co#1.0.0~dev: thisistrue.co#1.0.0
7 verbose lifecycle thisistrue.co#1.0.0~dev: unsafe-perm in lifecycle true
8 verbose lifecycle thisistrue.co#1.0.0~dev: PATH: C:\Users\Peter\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\projects\true\true\website\truevue\node_modules\.bin
9 verbose lifecycle thisistrue.co#1.0.0~dev: CWD: C:\projects\true\true\website\truevue
10 silly lifecycle thisistrue.co#1.0.0~dev: Args: [ '/d /s /c',
10 silly lifecycle 'cross-env NODE_ENV=development nodemon server/index.js --watch server' ]
11 silly lifecycle thisistrue.co#1.0.0~dev: Returned: code: 1 signal: null
12 info lifecycle thisistrue.co#1.0.0~dev: Failed to exec dev script
13 verbose stack Error: thisistrue.co#1.0.0 dev: `cross-env NODE_ENV=development nodemon server/index.js --watch server`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\Peter\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:317:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\Peter\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid thisistrue.co#1.0.0
15 verbose cwd C:\projects\true\true\website\truevue
16 verbose Windows_NT 10.0.17134
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Peter\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
18 verbose node v10.16.0
19 verbose npm v6.10.2-next.1
20 error code ELIFECYCLE
21 error errno 1
22 error thisistrue.co#1.0.0 dev: `cross-env NODE_ENV=development nodemon server/index.js --watch server`
22 error Exit status 1
23 error Failed at the thisistrue.co#1.0.0 dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Finally found an answer to this.
All I ended up doing was running npm update -g and it fixed the issue
Thanks all who helped, hope this can help someone else

I think you must add the path of node.js to the system variable
First: open Control Panel -> System and Security -> System -> Advanced System Settings -> Environment Variables
Second: in "User variables" or "System variables" find variable PATH and add node.js folder path as value.it is C:\Program Files\nodejs;If it doesn't exists, create it.
Third: Restart your computer.

npm start throwing error status 1 require is not a function

I get the following error when running npm start.
> app#0.1.0 start /Users/user/Desktop/react-tutorial
> react-scripts start
require(...) is not a function
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! app#0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the app#0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
Here is the actual error
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm#6.4.1
3 info using node#v10.15.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle app#0.1.0~prestart: app#0.1.0
6 info lifecycle app#0.1.0~start: app#0.1.0
7 verbose lifecycle app#0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle app#0.1.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/user/Desktop/react-tutorial/node_modules/.bin:/Library/Java/JavaVirtualMachines/jdk-9.0.4.jdk/Contents/Home/bin:/Users/user/Library/Android/sdk/tools:/Users/user/Library/Android/sdk/platform-tools:/Library/Frameworks/Python.framework/Versions/3.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Xamarin Workbooks.app/Contents/SharedSupport/path-bin:/opt/local/share/java/android-sdk-macosx/platform-tools:/Users/user/.android-sdk-macosx/platform-tools/:/Users/user/.android-sdk-macosx/platform-tools/:/Users/user/Library/Android/sdk/platform-tools/
9 verbose lifecycle app#0.1.0~start: CWD: /Users/user/Desktop/react-tutorial
10 silly lifecycle app#0.1.0~start: Args: [ '-c', 'react-scripts start' ]
11 silly lifecycle app#0.1.0~start: Returned: code: 1 signal: null
12 info lifecycle app#0.1.0~start: Failed to exec start script
13 verbose stack Error: app#0.1.0 start: `react-scripts start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:182:13)
13 verbose stack at maybeClose (internal/child_process.js:962:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid app#0.1.0
15 verbose cwd /Users/user/Desktop/react-tutorial
16 verbose Darwin 16.7.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v10.15.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error app#0.1.0 start: `react-scripts start`
22 error Exit status 1
23 error Failed at the app#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
This just started to happen when i restarted computer...why
I can't find anywhere where I am calling require()... maybe a plugin I installed?

In my case, had created a setupProxy.js file at project level, later i removed the configurations in it but not the file. Hence the mentioned error in question was thrown. To resolve, try one of the following according to your need,
update the proper configuration in the setupProxy.js
delete the setupProxy.js if not needed
don't leave the setupProxy.js as empty file

Delete nodes_modules
npm install -g npm
npm install & npm install -D
npm run start

Thanks to #Srinivas's response in the comment of the question.
Delete the generated setupProxy.js file. If you want to use a proxy, instead add it into your package.json file.
"proxy": "http://localhost:3000",
For a setupProxy.js file like so:
const proxy = require('http-proxy-middleware');
// tells the browser to direct any relative reference paths to the below
// domain instead of our own
module.exports = function(app) {
app.use(proxy('/api/*', { target: 'http://localhost:3000' }));*/
};

When you are setting up a Proxy to make a request to a different server
First Step is to install the dependency
npm install --save http-proxy-middleware
Next create setupProxy.js file
setupProxy.js
const { createProxyMiddleware } = require('http-proxy-middleware');
module.exports = function(app) {
app.use(
'/api',
createProxyMiddleware({
target: 'http://localhost:3001',
changeOrigin: true
})
);
};

npm script defined in package.json throws errors

I've installed the eslint package and added a series of scripts to package.json.
"scripts": {
"start": "node index.js",
"test": "node_modules/.bin/jasmine-node spec --color --verbose --autotest --watch .",
"acceptance": "node_modules/.bin/forever stopall && node_modules/.bin/forever start index.js && ./node_modules/.bin/jasmine-node test/ --verbose && node_modules/.bin/forever stopall",
"coverage": "./node_modules/.bin/istanbul cover -x **spec/** -x **index.js** -x **debug.js** jasmine-node spec",
"doc": "node_modules/.bin/jsdoc modules/",
"linter": "node_modules/.bin/eslint ."
}
When running these scripts I meet with mixed success. npm run test, nom run coverage, nom run doc all run without errors but npm run acceptance and npm run linter run the script then throw a series of errors, (I have copied the linter example below).
npm ERR! Darwin 16.0.0
npm ERR! argv "/Users/user/.nvm/versions/node/v6.7.0/bin/node"
"/Users/user/.nvm/versions/node/v6.7.0/bin/npm" "run" "linter"
npm ERR! node v6.7.0
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! todo#1.0.0 linter: `eslint .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the todo#1.0.0 linter script 'eslint .'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the todo package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! eslint .
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs todo
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls todo
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/user/Documents/todo/npm-debug.log
The acceptance tests won't even start the script before running. Why am I getting these errors? The contents of npm-debug.log are:
0 info it worked if it ends with ok
1 verbose cli [ '/Users/user/.nvm/versions/node/v6.7.0/bin/node',
1 verbose cli '/Users/user/.nvm/versions/node/v6.7.0/bin/npm',
1 verbose cli 'run',
1 verbose cli 'linter' ]
2 info using npm#3.10.3
3 info using node#v6.7.0
4 verbose run-script [ 'prelinter', 'linter', 'postlinter' ]
5 info lifecycle todo#1.0.0~prelinter: todo#1.0.0
6 silly lifecycle todo#1.0.0~prelinter: no script for prelinter, continuing
7 info lifecycle todo#1.0.0~linter: todo#1.0.0
8 verbose lifecycle todo#1.0.0~linter: unsafe-perm in lifecycle true
9 verbose lifecycle todo#1.0.0~linter: PATH: /Users/user/.nvm/versions/node/v6.7.0/lib/node_modules/npm/bin/node-gyp-bin:/Users/user/Documents/todo/node_modules/.bin:/Users/user/.nvm/versions/node/v6.7.0/bin:/Users/user/google-cloud-sdk/bin:/Library/Frameworks/Python.framework/Versions/3.5/bin:/Users/user/.nvm/versions/node/v6.7.0/bin:/opt/local/bin:/opt/local/sbin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/mysql/bin:/usr/texbin
10 verbose lifecycle todo#1.0.0~linter: CWD: /Users/user/Documents/todo
11 silly lifecycle todo#1.0.0~linter: Args: [ '-c', 'eslint .' ]
12 silly lifecycle todo#1.0.0~linter: Returned: code: 1 signal: null
13 info lifecycle todo#1.0.0~linter: Failed to exec linter script
14 verbose stack Error: todo#1.0.0 linter: `eslint .`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/Users/user/.nvm/versions/node/v6.7.0/lib/node_modules/npm/lib/utils/lifecycle.js:242:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (/Users/user/.nvm/versions/node/v6.7.0/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid todo#1.0.0
16 verbose cwd /Users/user/Documents/todo
17 error Darwin 16.0.0
18 error argv "/Users/user/.nvm/versions/node/v6.7.0/bin/node" "/Users/user/.nvm/versions/node/v6.7.0/bin/npm" "run" "linter"
19 error node v6.7.0
20 error npm v3.10.3
21 error code ELIFECYCLE
22 error todo#1.0.0 linter: `eslint .`
22 error Exit status 1
23 error Failed at the todo#1.0.0 linter script 'eslint .'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the todo package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error eslint .
23 error You can get information on how to open an issue for this project with:
23 error npm bugs todo
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls todo
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

NodeJS Cannot find module

My co-worker told me to checkout a Git repo that he's been working on.
The app uses NodeJS. I did "git clone" and then "npm install". My co-worker told me to then run "npm start". I tried this and I got an error. We decided the problem was my old version of Node. He was running with version 4 and I was way back on 0.6.
So I upgraded. I am on a Mac. I uninstalled Node using Homebrew, then re-installed Node using Homebrew.
Now:
node -v
v6.5.0
So now I do "npm install" and then "npm start". Now I get a different error:
npm start
> api-reference#0.0.1 start /Users/lLRK9/projects/zeria/api
> node server.js
module.js:457
throw err;
^
Error: Cannot find module './config/manifest.json'
at Function.Module._resolveFilename (module.js:455:15)
at Function.Module._load (module.js:403:25)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/Users/lLRK9/projects/zeria/api/server.js:5:18)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node/6.5.0/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.5.0
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! api-reference#0.0.1 start: `node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the api-reference#0.0.1 start script 'node server.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the api-reference package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node server.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs api-reference
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls api-reference
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/lLRK9/projects/zeria/api/npm-debug.log
cat /Users/lLRK9/projects/zeria/api/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/6.5.0/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'start' ]
2 info using npm#3.10.3
3 info using node#v6.5.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle api-reference#0.0.1~prestart: api-reference#0.0.1
6 silly lifecycle api-reference#0.0.1~prestart: no script for prestart, continuing
7 info lifecycle api-reference#0.0.1~start: api-reference#0.0.1
8 verbose lifecycle api-reference#0.0.1~start: unsafe-perm in lifecycle true
9 verbose lifecycle api-reference#0.0.1~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/lLRK9/projects/zeria/api/node_modules/.bin:/usr/local/Cellar/node/6.5.0/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Cellar/node/6.5.0/bin/node:/usr/local/bin/brew:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/mysql/bin
10 verbose lifecycle api-reference#0.0.1~start: CWD: /Users/lLRK9/projects/zeria/api
11 silly lifecycle api-reference#0.0.1~start: Args: [ '-c', 'node server.js' ]
12 silly lifecycle api-reference#0.0.1~start: Returned: code: 1 signal: null
13 info lifecycle api-reference#0.0.1~start: Failed to exec start script
14 verbose stack Error: api-reference#0.0.1 start: `node server.js`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:242:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid api-reference#0.0.1
16 verbose cwd /Users/lLRK9/projects/zeria/api
17 error Darwin 15.6.0
18 error argv "/usr/local/Cellar/node/6.5.0/bin/node" "/usr/local/bin/npm" "start"
19 error node v6.5.0
20 error npm v3.10.3
21 error code ELIFECYCLE
22 error api-reference#0.0.1 start: `node server.js`
22 error Exit status 1
23 error Failed at the api-reference#0.0.1 start script 'node server.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the api-reference package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node server.js
23 error You can get information on how to open an issue for this project with:
23 error npm bugs api-reference
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls api-reference
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
This app works for my co-worker. What differences in our setups might allow this app to work for him, but not for me?

Error: Cannot find module './config/manifest.json'
This looks like some local config file you're missing. You should ask him for it.
Alternatively, if there is an install hook in the package.json of the module, it may be attempting to configure this manifest.json file automatically, and it's possible that install script failed. You should check if there is any custom install hook as well.
(Also, I'd recommend using n in the future for managing Node.js versions).