Skip to content
This repository has been archived by the owner on Jan 6, 2021. It is now read-only.

chore(deps): update cross-spawn and trash-cli #14

Merged
merged 1 commit into from
May 20, 2016

Conversation

zhuangya
Copy link
Contributor

No description provided.

@@ -62,6 +62,7 @@
}
},
"dependencies": {
"cross-spawn": "^3.0.1",
"cross-spawn-async": "2.0.0",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we remove this now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated :)

On Thu, May 19, 2016 at 9:33 PM, Kent C. Dodds notifications@github.com
wrote:

In package.json
#14 (comment):

@@ -62,6 +62,7 @@
}
},
"dependencies": {

  • "cross-spawn": "^3.0.1",
    "cross-spawn-async": "2.0.0",

Should we remove this now?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/kentcdodds/cross-env/pull/14/files/0d755a90a7de1bca72403e957eaffacaa69043c7#r63878305

@kentcdodds
Copy link
Owner

Hi @zhuangya. This PR looks great. I'm unsure of the benefit of using cross-spawn vs cross-spawn-async. They both look to be maintained by the same developer and they both received a release in the last 24 hours so they both look actively maintained. Could you explain the reasoning behind that update? Thanks!

@kentcdodds
Copy link
Owner

And actually, we should probably be using rimraf instead of trash so we don't fill up the Recycle bin... ¯_(ツ)_/¯

@zhuangya
Copy link
Contributor Author

Yeah. No problem. But currently it's around 1 am in my timezone I really need to have some sleep
I'll change it later. -)
Sent using CloudMagic Email [https://cloudmagic.com/k/d/mailapp?ct=pi&cv=7.11.40&pv=9.3.1&source=email_footer_2]
On 周五, 5月 20, 2016 at 01:23, Kent C. Dodds notifications@github.com wrote:
And actually, we should probably be using rimraf instead of trash so we don't fill up the Recycle bin... ¯_(ツ)_/¯


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub [https://github.com//pull/14#issuecomment-220393778]

@kentcdodds
Copy link
Owner

Cool, have a good night! 💤

Also, if you could explain why we need to change to cross-spawn, that'd be great :-)

@zhuangya
Copy link
Contributor Author

trash => rimraf

why switch to cross-spawn, cause cross-spawn-async is deprecated

@codecov-io
Copy link

Current coverage is 100%

Merging #14 into master will not change coverage

@@           master   #14   diff @@
===================================
  Files           1     1          
  Lines          32    32          
  Methods         0     0          
  Messages        0     0          
  Branches        0     0          
===================================
  Hits           32    32          
  Misses          0     0          
  Partials        0     0          

Powered by Codecov. Last updated by afc91b7...4146b27

@kentcdodds kentcdodds merged commit 22bf76d into kentcdodds:master May 20, 2016
@kentcdodds
Copy link
Owner

Thanks a bunch!

@zhuangya zhuangya deleted the cross-spawn branch May 20, 2016 03:09
@zhuangya
Copy link
Contributor Author

bump a new version on npm maybe?
thanks 😄

@kentcdodds
Copy link
Owner

Is there a reason that's necessary? It's working as is right?

@zhuangya
Copy link
Contributor Author

❯ npm install cross-env
npm WARN deprecated cross-spawn-async@2.0.0: cross-spawn no longer requires a build toolchain, use it instead!

@kentcdodds
Copy link
Owner

Ah, ok. I'll try to get something released soon. Thanks.

@zhuangya
Copy link
Contributor Author

no hurry since everything works fine now.

nice day =)

On Tue, May 24, 2016 at 11:59 AM, Kent C. Dodds notifications@github.com
wrote:

Ah, ok. I'll try to get something released soon. Thanks.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#14 (comment)

@kentcdodds
Copy link
Owner

It should be released now. 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants