-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Comments
I'm having the same problems.
|
Got similar report on SBoudrias/Inquirer.js#447 Looks like Windows and Node 7 don't play well with one of our dependency. |
Curiously enough I have no problems with Windows 10 and Node 7.1.0 running in a VM: 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. |
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 |
Regarding nodejs/node#9542 it looks like errors are caused by a Node.js regression. Current workaround: Get back to Node |
mischah, you are right! |
Closing this since Node 7.2 fixes this issue: |
@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. |
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! |
i have downgrade version, and now work perfectly |
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:Error message states:
The text was updated successfully, but these errors were encountered: