Can't create dashboard on windows

[Oliver Sträßer]

C:\Users\osr\Documents\nodejs>atlasboard new testdashboard

Generating a new AtlasBoard project at C:\Users\osr\Documents\nodejs\testdashboard...

Directory C:\Users\osr\Documents\nodejs\testdashboard/ does not exist. Creating it no w. Porting sample project across... Installing npm dependencies...

Error installing dependencies. Please run "npm install" inside the dashboard dir ectory

C:\Users\osr\Documents\nodejs>cd testdashboard

C:\Users\osr\Documents\nodejs\testdashboard>npm install

C:\Users\osr\Documents\nodejs\testdashboard>atlasboard start

Checking npm dependencies for C:\Users\osr\Documents\nodejs\testdashboard\packages\de mo... Error installing dependencies for C:\Users\osr\Documents\nodejs\testdashboard\package s\demo. err:Error: spawn ENOENT

C:\Users\osr\Documents\nodejs\testdashboard>

[Oliver Sträßer]

I tried to use the last comiited version as well, same issue :-( perhaps you have an idea to solve my problem.

I'm using windows 8.1

[Cavedale DD]

I am having the same issue as well, Using the latest node version 0.10.24

On windows 7

[Iván Loire]

We don't really use windows, but it may be a permission related issue.

You can just install the dependencies manually (it is what atlasboard is trying to do there) by doing "npm install" in every package directory (in this case, packages\demo)

[Bill Barekas]

I have the same issue. I cannot npm install manual anything. - Top-level package.json has empty dependencies list. - Also there is no package.json in the packages\demo folder.

[Neville Franks]

Same problem here. I have packages.json in packages/demo and in mydashboard and have run npm install in those directories. Windows 8.

[Joe Bott]

It worked for me after replacing the string 'npm' (including quotes) with 'npm.cmd' in both atlasboard\lib\package-dependency-manager.js and atlasboard\lib\cli\commands.js.

Before the change I saw in Process Monitor that it was trying to start either a "npm.exe" or a "npm.com". Not sure why it'd try those but not "npm.cmd"

[Seik0815]

@ Joe Bott: Thanks, worked for me too!

[Yoann Ciabaud]

This solution works for me on win7 64bits wih VS2013. Thanks Joe Bott

[Doug Copestake]

Submitted a pull request to hopefully resolve this.

[Iván Loire]

Fixed in 0.12.0

[Heng-Shou Liu]

@ Joe Bott: Thanks, worked for me too!