From 71b6b990c8b599d8b81036d553302c2840e089ac Mon Sep 17 00:00:00 2001 From: Anthony Cook Date: Tue, 13 Dec 2016 12:17:17 +0000 Subject: [PATCH] Update package.json NODE_ENV is not a recognised command on Windows, the work around is to use the cross-env package or to have two separate scripts, one for Windows and one for Unix based systems. I figured using the cross-env is much more friendly and will save confusion, tested on both Windows and Mac. --- examples/auth-routes/package.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/examples/auth-routes/package.json b/examples/auth-routes/package.json index b286e52738..87677b2922 100644 --- a/examples/auth-routes/package.json +++ b/examples/auth-routes/package.json @@ -3,6 +3,7 @@ "description": "", "dependencies": { "body-parser": "^1.15.2", + "cross-env": "^3.1.3", "express": "^4.14.0", "express-session": "^1.14.2", "nuxt": "latest", @@ -11,6 +12,6 @@ "scripts": { "dev": "node server.js", "build": "nuxt build", - "start": "NODE_ENV=production node server.js" + "start": "cross-env NODE_ENV=production & node server.js" } }