On Thu, Oct 19, 2017 at 2:48 PM, Joe Orr <[email protected]> wrote: > You can also get the newest versions from the project repo, run 'npm run > build' >
This fails for me. The contents of npm-debug.log is: 0 info it worked if it ends with ok 1 verbose cli [ 'C:\\PROGRA~1\\nodejs\\node.exe', 1 verbose cli 'C:\\PROGRA~1\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'run', 1 verbose cli 'build' ] 2 info using [email protected] 3 info using [email protected] 4 verbose stack Error: ENOENT: no such file or directory, open 'c:\Web\leo-examples\package.json' 4 verbose stack at Error (native) 5 verbose cwd c:\Web\leo-examples 6 error Windows_NT 10.0.15063 7 error argv "C:\\PROGRA~1\\nodejs\\node.exe" "C:\\PROGRA~1\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build" 8 error node v4.4.4 9 error npm v2.15.1 10 error path c:\Web\leo-examples\package.json 11 error code ENOENT 12 error errno -4058 13 error syscall open 14 error enoent ENOENT: no such file or directory, open 'c:\Web\leo-examples\package.json' 14 error enoent This is most likely not a problem with npm itself 14 error enoent and is related to npm not being able to find a file. 15 verbose exit [ -4058, true ] Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
