Update cross-env to version 4.0.0 🚀

Hello lovely humans,

cross-env just published its new version 4.0.0.

State	Update :rocket:
Dependency	cross-env
New version	4.0.0
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of cross-env. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

GitHub Release

4.0.0 (2017-03-31)

Bug Fixes

Resolve value of env variables before invoking cross-spawn (#95) (e8a16146)
Remove Windows => UNIX variable conversion (#94) (0a846e60)
module: Add export for commonjs (#88) (22d1c801)

Features

Convert list delimiters for PATH-style env variables (#93) (ea0ac4bd)
args: convert embedded and braced variables in command args (#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)

The new version differs by 39 commits .

e8a1614 fix: Resolve value of env variables before invoking cross-spawn (#95)
9e0ea05 docs(engine): revert support to node 4 (#96)
0a846e6 fix: Remove Windows => UNIX variable conversion (#94)
ea0ac4b feat: Convert list delimiters for PATH-style env variables (#93)
ea80021 feat(spawn): add support for quoted scripts
22d1c80 fix(module): Add export for commonjs (#88)
1b172fe feat(args): convert embedded and braced variables in command args (#86)
c1a9ed0 fix(args): make args conversion stateless (#85)
920451d docs(contributors): add @inyono (#83)
b59473a docs(contributors): add @danielo515 (#81)
4799cc2 docs(README): Add compumike08 as a contributor (#79)
4fceddd docs(badges): add appveyor badge
80b382e chore(build): add appveyor (#76)
cdffc6e docs: fix contributing nps references
a154170 docs: add wopian as contributor (#73)

There are 39 commits in total. See the full diff.

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

dtinth / babel-plugin-coverage