Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update cross-env to the latest version 🚀 #8

Merged
merged 1 commit into from
Apr 3, 2017

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented Mar 31, 2017

Version 4.0.0 of cross-env just got published.

Dependency cross-env
Current Version 3.2.4
Type devDependency

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.0

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)
Commits

The new version differs by 7 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)

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 🌴

@adamisntdead adamisntdead merged commit 1abc5ed into master Apr 3, 2017
@greenkeeper greenkeeper bot deleted the greenkeeper/cross-env-4.0.0 branch April 3, 2017 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant