unable to 'npm start' a local server on Windows 7 // Unix-style NODE_ENV variable assignment issue

[micahstubbs]

this answer over at stackoverflow suggests that for Windows the command
NODE_ENV=development nodemon --watch app --watch public/js server js
should be something like
SET NODE_ENV=development nodemon --watch app --watch public/js server js

http://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman

[micahstubbs]

tried the advice here, without success

http://stackoverflow.com/questions/9249830/how-can-i-set-node-env-production-in-windows

[mathisonian]

@micahstubbs are you able to run it without the NODE_ENV flag?

e.g. just

$ node server.js

as the most basic way to start it up?

[micahstubbs]

result from running

$ node server.js

will try to resolve the ImageMagick dependency and report back

[micahstubbs]

after installing ImageMagick ImageMagick-6.9.1-2-Q16-x64-dll.exe

I run

$ node server.js

and see

[micahstubbs]

I do see Lightning running on localhost:3000

[mathisonian]

@micahstubbs it seems to be the git clone that is causing things to fail (we use git under the hood to fetch the visualizations remotely). I'm guessing if you go into "visualization types" you won't see anything.

Do windows users typically not have a git command on the command line? We use gift under the hood to handle the actual interaction with git commands

[micahstubbs]

@mathisonian good question. On Windows I use Git Bash and and MinGW, which is a port of a Linux style environment and command line tools.

http://stackoverflow.com/questions/16757393/what-is-the-difference-between-git-bash-and-the-github-for-windows-shell