-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
ReadStream: Cannot read property 'prototype' of undefined #109
Comments
I can confirm the issue. |
I have the same problem |
same here,using webpack2 & react |
+1 having this issue |
i have the same problem with react and webpack |
I have the same problem as well when trying to require mongodb. fs does contain ReadStream |
I have the same problem with create-react-app |
I have the same issue with a clean project that i created with create-react-app. |
+1 having same issue |
Hi all, Maybe anyone has the same constelation and problem. |
i have same issue. npm i chalk@2.0.1 it work fine. i think it would help some one! |
I have the same problem; |
@medkhelifi did't you try replace your chalk version to 2.0.1? |
I am having the same issue. Any updates? I used create-react-app and ejected it. |
+1 |
using electron with nodejs. updating chalk version to 2.0.1 => did not work for me. |
with FS you are trying to get file from clients computer? fs must be used on back ) no webpack |
Dear Isaacs, Best regards, Anela. |
Here is how I fixed it:
this works because in the docs there are create methods for creating streams. |
Issue not fully resolved on my end after applying @spirosbax's fix manually. See: #135 (comment) |
@rekmarks yeah, just think about when using git... nobody would ever include the node_modues folder |
This issue should be resolved by latest graceful-fs. Please let us know if you continue to have problems after updating. |
I am getting this issue:
#70
On these lines:
https://github.com/isaacs/node-graceful-fs/blob/master/graceful-fs.js#L165-L166
But I am NOT on Meteor. I am using Angular2
The text was updated successfully, but these errors were encountered: