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

"Stream" is read-only error on run-time (occurred after migration from RN 0.53.3 to 0.56) #20415

Closed
3 tasks done
ketn opened this issue Jul 26, 2018 · 5 comments
Closed
3 tasks done
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@ketn
Copy link

ketn commented Jul 26, 2018

Environment

React Native Environment Info:
System:
OS: macOS Sierra 10.12.2
CPU: x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 640.39 MB / 8.00 GB
Shell: 3.2.57 - /bin/sh
Binaries:
Node: 10.7.0 - /usr/local/bin/node
Yarn: 1.7.0 - /usr/local/bin/yarn
npm: 6.2.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 10.3, macOS 10.12, tvOS 10.2, watchOS 3.2
IDEs:
Android Studio: 3.1 AI-173.4819257
Xcode: 8.3.3/8E3004b - /usr/bin/xcodebuild
npmPackages:
react: 16.4.1 => 16.4.1
react-native: 0.56.0 => 0.56.0
npmGlobalPackages:
react-native-cli: 2.0.1

Description

I just migrated from react-native@0.53.3 to react-native@0.56. Also, as required, upgraded my node to 8+ (10.7.0) and babel to 7.0.0-beta.54. After completing the migration process, the following error showed up:

rn-0 56-error

Here are babel devDependencies:

"devDependencies": {
"@babel/core": "7.0.0-beta.54",
"@babel/preset-flow": "7.0.0-beta.54",
"babel-core": "^7.0.0-bridge.0",
"babel-jest": "22.1.0",
"babel-preset-react-native": "5.0.2",
"jest": "22.1.4",
"react-test-renderer": "16.2.0"
},
"jest": {
"preset": "react-native"
}

I cannot find an issue similar to this anymore, hence posted it over here. Am I doing something wrong?

@john-hu
Copy link

john-hu commented Jul 27, 2018

+1. I had met the same issue after migrating to RN 0.56. My app depends on react-native-cheerio which uses a library to override Stream that causes this issue. I don't know why. But it works well at previous version, RN 0.49.3......

@ketn
Copy link
Author

ketn commented Jul 27, 2018

@john-hu Thanks. Fixed for me after uninstalling react-native-cheerio. Is there any way to allow overriding Stream?

@john-hu
Copy link

john-hu commented Jul 27, 2018

It's just a workaround. I think the issue still exist. I don't know how to make Stream overridable....

@stale
Copy link

stale bot commented Oct 25, 2018

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Oct 25, 2018
@stale
Copy link

stale bot commented Nov 1, 2018

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Nov 1, 2018
@facebook facebook locked as resolved and limited conversation to collaborators Nov 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

2 participants