Doesn't work on Windows

Spudz76 commented 10 years ago

lib/run.js needs os awareness hacked in such as here: https://github.com/Concurix/concurixjs/commit/70fcdf5207af955af266d328f45bc14d03275341

child-process does not work on Windows, among other things, but at the moment I get the "errno 193" problem right after the git checkout succeeds.

Bruce17 commented 9 years ago

Same here. I get the following error:

C:\path> wicked --toc --nocommit                                       
info wicked Cloning wiki from git@github.com:user/myrepo.wiki.git                                       
Cloning into 'wiki'...                                                                                         
remote: Counting objects: 3, done.                                                                             
remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0                                                   
Receiving objects: 100% (3/3), done.                                                                           
Checking connectivity... done.                                                                                 
child_process.js:1162                                                                                          
    throw errnoException(err, 'spawn');                                                                        
          ^                                                                                                    
Error: spawn UNKNOWN                                                                                           
    at exports._errnoException (util.js:746:11)                                                                
    at ChildProcess.spawn (child_process.js:1162:11)                                                           
    at exports.spawn (child_process.js:995:9)                                                                  
    at run (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\run.js:27:14)                             
    at runJsdoc (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\run-jsdoc.js:44:3)                   
    at runnel (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\node_modules\runnel\index.js:77:10)        
    at updateWiki (C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\index.js:77:5)                         
    at C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\index.js:82:5                                      
    at C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\clone-wiki.js:65:7                             
    at C:\Users\mir\AppData\Roaming\npm\node_modules\wicked\lib\clone-wiki.js:37:7

I'm using: Win7 x64

seangenabe commented 8 years ago

I'm getting this too. This is caused by "directly" spawning the .js file (node_modules/jsdoc/jsdoc.js). Please consider wrapping the spawn call with node.

BTW this works on Unix because of the hashbang.

A-312 commented 5 years ago

https://github.com/thlorenz/wicked/blob/b87d2762c14e4ab8d7920bc372cca18f84389884/lib/run-jsdoc.js#L44

can be replaced by :

  run('node ' + jsdoc, args, projectroot, function (err) {

thlorenz / wicked

Doesn't work on Windows #8