Windows 8 npm start error.

[tomshaw]

npm start fails

Following the blogger instructions npm start fails. I can almost get Ghost working via the developer instructions but it stalls on the task compass:compile, different issue. I do have all required dependencies installed.

npm debug log

ghost@0.4.1 start C:\Node\cloned\ghost
node index

module.js:340
throw err;
^
Error: Cannot find module './loader'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (C:\Node\cloned\ghost\core\server\config\index.js:6:21)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

npm ERR! ghost@0.4.1 start: node index
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the ghost@0.4.1 start script.
npm ERR! This is most likely a problem with the ghost package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node index
npm ERR! You can get their info via:
npm ERR! npm owner ls ghost
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js"
"start"
npm ERR! cwd C:\Node\cloned\ghost
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.24
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Node\cloned\ghost\npm-debug.log
npm ERR! not ok code 0

[javorszky]

Actually, nvm the previous one, I haven't had enough coffee yet.

[Dradden]

https://ghost.org/forum/installation/1297-error-cannot-find-module-when-upon-starting/

[ErisDS]

From the information provided, it seems this is an environment issue, as opposed to a bug in Ghost. I'm closing this as GitHub is for tracking active issues. For more information about raising issues on GitHub please see our contributing guidelines.

If anyone here knows the answer they will still reply, but you may find the forum is a better place to get support.