ELIFECYCLE error on npm run dev/prod about isomorphic500 HOT 6 CLOSED

Hi @shelakel, thanks! Fluxible-router is coming soon :-)

It's a problem setting env vars:

NODE_ENV=development DEBUG=isomorphic500 node index

On windows this should work:

SET NODE_ENV=development 
SET DEBUG=isomorphic500 
node index

Please try and comment with the results 👍

from isomorphic500.

Good stuff.

It seems that using Command Prompt (cmd.exe) fails to start the webpack development server.

Run: cmd.exe /C "set NODE_ENV=development && set DEBUG=isomorphic500 && node index"

Only bash works on Windows. I think opting for the webpack/react-starter scripts approach is more feasible in the long run.

from isomorphic500.

@shelakel seconded. I think setting environment vars in the JS is more OS agnostic.
NODE_ENV=development DEBUG=isomorphic500 node index directly in bash did the trick for me, thanks! And thanks @gpbl for the awesome reference!

from isomorphic500.

If you're interested, the following works for me (Windows 8.1). In package.json:

"dev": "node index --dev --DEBUG=isomorphic500"

Then in index.js I catch/store any flags:

var args = require('yargs').argv;

if (args.dev) process.env.NODE_ENV = 'development'; // either catch flags specifically

if (args.DEBUG) {
    process.env.DEBUG = args.DEBUG; // or just set whatever's passed in to some flag
}

// Start the server app
require("./src/server");

from isomorphic500.

Thanks @davidgilbertson for the suggestion! However i'd go for setting the env vars out of the npm script.

from isomorphic500.

https://www.npmjs.com/package/cross-env

from isomorphic500.