-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 ENOENT: no such file or directory, open '...AppFolder\node_modules\@types\node\README.md' at Error (native) #919
Comments
it just installed without any errors
|
I am facing the same issue with recent version of Yarn v0.16.1 on windows 7. The problem is somewhat indeterministic but in complex projects when I have modified package.json then yarn fails on the first run of "Linking dependencies". When I then run yarn again it works fine. BTW: I am a user of maven for Java since years. There you have a central repository what is probably the cache folder of yarn in appdata is about. However, instead of duplicating mega- or gigabytes on the disc why dont you just create symlinks (yes also on windows) for the folders in node_modules? I already discussed such things with npm community and gave up as they do not care. Maybe yarn will cure the pain... |
Same problem here on Windows 7 x64 with Node 6.7.0 (when trying to install various packages). |
Same issue here.
Output:
|
Sounds like this issue should be reopened or do we need to file a new issue? |
Currently I have the effect that I get this ENOENT every time I call |
I'm having the same issue with
|
is it has been fixed? |
as a temporal workaround on our build server: |
@rkusuma those issues refers to windows users, and windows users should suffer =) |
I'm having an identical issue on windows 10, Node v6.9.1 running it in Powershell:
Pretty much makes Yarn completely unusable on Windows machines. |
@AntJanus I think it is a little bit different issue, the original issue is about disappearing modules from project's node_modules, not cache. |
@whitecolor time to file a new issue then! Thanks! |
I have the same problem. Most of the time
Windows 8.1 @manrueda How do you print that pretty table for your specs? |
I noticed that @wesamco, @marcomorain, and me all have "fsevents" in their output logs. Coincidence? |
@centigrade-thomas-becker it can be easily reproduced following this steps:
ie this bug appears anytime you change your |
It's the same for me - it happens after adding a package from the types user namespace on npm to package.json |
Seems to be fixed by #1861 but is not yet released. I tested it on master. |
The referenced issue is now marked as resolved: #1861 |
I can confirm that it was fixed. cc @bestander |
Thanks, let's close this then |
Do you want to request a feature or report a bug? Bug
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.
yarn add angular2-apollo --save
What is the expected behavior?
install Node package correctly without this unnecessary error
Please mention your node.js, yarn and operating system version.
Yarn v0.15.1
install method: MSI installer from website.
OS: Windows 10 Pro Version 1607 (OS Build 14393.321)
The text was updated successfully, but these errors were encountered: