Update cross-env to the latest version 🚀 #431
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 4.0.0 of cross-env just got published.
The version 4.0.0 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.
Release Notes
v4.0.04.0.0 (2017-03-31)
Bug Fixes
Features
Breaking Changes
FOO=$BAR
with the value$BAR
being assigned tohello
, the command will be converted toFOO=hello
whereas before it wasFOO=$BAR
).(e8a16146)
(0a846e60)
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)
(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)
Commits
The new version differs by 31 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 31 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴