cross-env versions available: 5.0.0, 4.0.0

[dependencies]

There are new versions of cross-env available from npm.

5.0.0

5.0.0 (2017-05-11)

Bug Fixes

• bin: add a bin entry for cross-env-shell (9c4f3462)

Features

• don't change colons on non-PATH/NODE_PATH on win32 (Adds support for preLoaders in custom webpack config #107) (38814238)
• bin: two bins (shell, non-shell) (Add React Developer Tools hook #104) (d7b48d5c, closes #99)

Breaking Changes

• Scripts using quotes or escape sequences will see a difference in behavior.
  Switching to the second bin should resolve any issue.

Closes #99.

(d7b48d5c)

4.0.0

4.0.0 (2017-03-31)

Bug Fixes

• Resolve value of env variables before invoking cross-spawn (Failure parsing .babelrc with comments #95) (e8a16146)
• Remove Windows => UNIX variable conversion (Added fixed height and lineHeight to search box #94) (0a846e60)
• module: Add export for commonjs (Create a static storybook builder #88) (22d1c801)

Features

• Convert list delimiters for PATH-style env variables (Separate CSS files #93) (ea0ac4bd)
• args: convert embedded and braced variables in command args (Implement linkTo functionality #86) (1b172fef)
• spawn: add support for quoted scripts (ea800213)

Breaking Changes

• This is unlikely to break anyone, but now if you assign a variable to a variable (like FOO=$BAR with the value $BAR being assigned to hello, the command will be converted to FOO=hello whereas before it was FOO=$BAR).
  (e8a16146)
• %windows_style% env variables will no longer be converted to $unix_style in UNIX machines. To fix it, use always the UNIX syntax, cross-env will change the format in Windows machines as needed
  (0a846e60)
• If an env variable has : or ; in its value, it will be converted to : on UNIX
  systems or ; on Windows systems. To keep the old functionality, you will need to escape those
  characters with a backslash.

#80

• chore: Add myself (DanReyLop) to the contributors list

• Simplified logic. Now only : (UNIX-style) are converted to ; (Windows-style), not the other way around

BREAKING CHANGE: You now must escape : to use it in a value of you don't want it to be swapped with ; on Windows
(ea0ac4bd)

• Changes the behavior when passed quoted scripts or special characters interpreted by the shell.
  (ea800213)
• echo $var2/$var1 would not be changed on windows, now it is. This is kind of a bug, but we're doing a major version bump to be safe.
  (1b172fef)

[Hypnosphi]

Handled by #2051