Support quoted scripts

README.md

@@ -87,6 +87,19 @@ the parent. This is quite useful for launching the same command with different
 env variables or when the environment variables are too long to have everything
 in one line.
 
+## Gotchas
+
+If you want to have the environment variable apply to several commands in series
+then you will need to wrap those in quotes in your script. For example:
+
+```json
+{
+  "scripts": {
+    "greet": "cross-env GREETING=Hi NAME=Joe \"echo $GREETING && echo $NAME\""
+  }
+}
+```
+
 ## Inspiration
 
 I originally created this to solve a problem I was having with my npm scripts in

package.json

@@ -7,7 +7,7 @@
     "cross-env": "dist/bin/cross-env.js"
   },
   "engines": {
-    "node": ">=4.0"
+    "node": ">=4.8"
   },
   "scripts": {
     "start": "nps",

src/index.js

@@ -8,7 +8,11 @@ const envSetterRegex = /(\w+)=('(.+)'|"(.+)"|(.+))/
 function crossEnv(args) {
   const [command, commandArgs, env] = getCommandArgsAndEnvVars(args)
   if (command) {
-    const proc = spawn(command, commandArgs, {stdio: 'inherit', env})
+    const proc = spawn(command, commandArgs, {
+      stdio: 'inherit',
+      shell: true,
+      env,
+    })
     process.on('SIGTERM', () => proc.kill('SIGTERM'))
     process.on('SIGINT', () => proc.kill('SIGINT'))
     process.on('SIGBREAK', () => proc.kill('SIGBREAK'))

src/index.test.js

@@ -80,6 +80,7 @@ function testEnvSetting(expected, ...envSettings) {
   expect(crossSpawnMock.spawn).toHaveBeenCalledTimes(1)
   expect(crossSpawnMock.spawn).toHaveBeenCalledWith('echo', ['hello world'], {
     stdio: 'inherit',
+    shell: true,
     env: Object.assign({}, process.env, env),
   })