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

Error running yo with Node.js 7.1 on windows 10 (Error: write EINVAL) #485

Closed
jochenvanwylick opened this issue Nov 9, 2016 · 14 comments
Closed

Comments

@jochenvanwylick
Copy link

After updating Node to latest version ( 7.1.0 ) on my windows 10 box, I globally installed yeoman. After that, I get an error running the yo command:

yeoman_error

Error message states:

D:\_code\test>yo
C:\Users\Jochen\AppData\Roaming\npm\node_modules\yo\node_modules\rx-lite\rx.lite.js:75
    throw e;
    ^

Error: write EINVAL
    at exports._errnoException (util.js:1022:11)
    at WriteStream.Socket._writeGeneric (net.js:715:26)
    at WriteStream.Socket._write (net.js:734:8)
    at doWrite (_stream_writable.js:334:12)
    at writeOrBuffer (_stream_writable.js:320:5)
    at WriteStream.Writable.write (_stream_writable.js:247:11)
    at WriteStream.Socket.write (net.js:661:40)
    at MuteStream.ondata (stream.js:31:26)
    at emitOne (events.js:96:13)
    at MuteStream.emit (events.js:188:7)

D:\_code\test>npm -v
3.10.9

D:\_code\test>node -v
v7.1.0
@mischah
Copy link
Member

mischah commented Nov 9, 2016

Mhmm. No Problems with Node 7.1.0 on Mac OS.

image

@longjoel
Copy link

I'm having the same problems.


Error: write EINVAL
    at exports._errnoException (util.js:1022:11)
    at WriteStream.Socket._writeGeneric (net.js:715:26)
    at WriteStream.Socket._write (net.js:734:8)
    at doWrite (_stream_writable.js:334:12)
    at writeOrBuffer (_stream_writable.js:320:5)
    at WriteStream.Writable.write (_stream_writable.js:247:11)
    at WriteStream.Socket.write (net.js:661:40)
    at MuteStream.ondata (stream.js:31:26)
    at emitOne (events.js:96:13)
    at MuteStream.emit (events.js:188:7)

@SBoudrias
Copy link
Member

Got similar report on SBoudrias/Inquirer.js#447

Looks like Windows and Node 7 don't play well with one of our dependency.

@mischah
Copy link
Member

mischah commented Nov 10, 2016

Curiously enough I have no problems with Windows 10 and Node 7.1.0 running in a VM:

image

So it would be awesome if @longjoel @jochenvanwylick or @Lichtjaeger could deep a little deeper to check if its only rx-lite which make problems. If so you could file a bug in the RxJS Repo.

@Lichtjaeger
Copy link

Sorry, but that is not the same Windows Version I run. I have the latest Windows (10.0.14393 Build 14393 | Anniversary 2016).

These are my error states:

If I run yo in my cmd (or PowerShell too) it displays only black:
schnappschuss_111016_111711_am
After resize I get these error:
schnappschuss_111016_111755_am

If I run yo <generator_name> a get the following error:
schnappschuss_111016_111900_am

@mischah
Copy link
Member

mischah commented Nov 10, 2016

Interestingly other users have similar errors with the combination of Windows 10 and Node 7.1.0 in with different packages:

I filed an issue in the Node.js repo: nodejs/node#9542

@mischah
Copy link
Member

mischah commented Nov 10, 2016

Regarding nodejs/node#9542 it looks like errors are caused by a Node.js regression.

Current workaround: Get back to Node 7.0.0 or better use the current LTS version 6.9.x

@diegocapadi
Copy link

mischah, you are right!

@mischah mischah changed the title Error running yo in yo\node_modules\rx-lite\rx.lite.js:75 Error running yo with Node.js 7.1 on windows 10 (Error: write EINVAL) Nov 22, 2016
@mischah
Copy link
Member

mischah commented Nov 23, 2016

Closing this since Node 7.2 fixes this issue:
https://nodejs.org/en/blog/release/v7.2.0/

@mischah mischah closed this as completed Nov 23, 2016
@jochenvw
Copy link

Yep - confirmed - thanks!

image

@HelloPb
Copy link

HelloPb commented Dec 2, 2016

I am getting error on windows 10, with node 7.2 latest
image

@Lichtjaeger
Copy link

Lichtjaeger commented Dec 2, 2016

@HelloPb I've made the experience that npm renames a file named ".gitignore" to ".npmignore".

You can confirm this by looking in the "C:\Users\Prasanna\AppData\Roaming\npm\node_modules\generator-fwsp-hydra\app\templates" directory.

It's a problem with the "generator-fwsp-hydra" module. Not with yo.

@emadum
Copy link

emadum commented Jan 5, 2017

Hi @HelloPb, just had this thread called to my attention. We fixed this issue a few days after your post, so if you haven't already, updating to the latest version of generator-fwsp-hydra will fix it.

Thanks!

@arigates
Copy link

i have downgrade version, and now work perfectly

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

No branches or pull requests

10 participants