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

spawn ENOENT error [and possible fix?] #2

Closed
NogsMPLS opened this issue Nov 11, 2015 · 1 comment · Fixed by #3
Closed

spawn ENOENT error [and possible fix?] #2

NogsMPLS opened this issue Nov 11, 2015 · 1 comment · Fixed by #3

Comments

@NogsMPLS
Copy link
Contributor

Running windows 7, node 4.2.2 x64 bit, npm 2.14.7.

I get the following error when using cross-env:

cross-env-error

After a bunch of digging around, I found that if I replace the usage of spawn in cross-env with cross-spawn (https://www.npmjs.com/package/cross-spawn) the issue goes away for me.

I can put in a PR if you think adding this dependency is alright.
@kentcdodds
Copy link
Owner

Yes! Please do! I ended up creating argv-set-env because of this problem and I haven't come back to find out what the root issue was. I look forward to your PR 👍

@NogsMPLS NogsMPLS mentioned this issue Nov 11, 2015
Merged
kentcdodds pushed a commit that referenced this issue Nov 11, 2015
@NogsMPLS
fix(spawn): use cross-spawn for spawn compatibility
3c21e49 
(cherry picked from commit 9be84e4)
originally by [@NogsMPLS](https://github.com/NogsMPLS) in #3 as
mentioned in #2

closes #2
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

use cross-spawn for spawn compatibility NogsMPLS/cross-env
2 participants
@kentcdodds @NogsMPLS