Install failure

Hello… following the instructions for running locally (I have installed node.js) - failure at the npm run jspm-install step. There is no npm-debug.log file that I can see - console output below. Thanks!

[09:21:48] Starting ‘bundle’… [09:21:49] ‘bundle’ errored after 1.15 s [09:21:49] Error on fetch for redoc.module.js at file:///C:/ReDoc/redoc.module.j s Loading .tmp\lib\index.js Error: ENOENT: no such file or directory, open 'C:\ReDoc\redoc.module.js ’ at Error (native) [09:21:49] ‘build’ errored after 5.6 s [09:21:49] Error in plugin ‘run-sequence(bundle)’ Message: Error on fetch for redoc.module.js at file:///C:/ReDoc/redoc.module.js Loading .tmp\lib\index.js ENOENT: no such file or directory, open ‘C:\ReDoc\redoc.module.js’ Details: originalErr: Error: ENOENT: no such file or directory, open ‘C:\ReDoc\redoc. module.js’ Stack: Error on fetch for redoc.module.js at file:///C:/ReDoc/redoc.module.js Loading .tmp\lib\index.js Error: ENOENT: no such file or directory, open 'C:\ReDoc\redoc.module.js ’ at Error (native) npm ERR! Windows_NT 6.1.7601 npm ERR! argv “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js” “start” npm ERR! node v4.5.0 npm ERR! npm v2.15.9 npm ERR! code ELIFECYCLE npm ERR! redoc@1.1.2 start: gulp serve npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the redoc@1.1.2 start script ‘gulp serve’. npm ERR! This is most likely a problem with the redoc package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! gulp serve npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs redoc npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm ERR! npm owner ls redoc npm ERR! There is likely additional logging output above.

[fcaprilli]

p.s. very excited about this - it’s exactly what I’ve been looking for!

[RomanHotsiy]

@fcaprilli I’ve checked your spec and this is a ReDoc bug. I reported it as a separate issue - #84 Will try to ship the fix in the next release