Summary: ReactNativeFlipperExample crashed as soon as a running app tried to connect to the Metro instance, which turns out to be caused by a pinned `ws`. Luckily someone else experienced this before, would have taken a while otherwise :-P, as the error is not logged in Metro, and on Flipper side we just receive a super generic error message https://github.com/facebook/metro/issues/678#issuecomment-865835602 Reviewed By: nikoant Differential Revision: D29515730 fbshipit-source-id: 2524f85338c9b93d8bcf31b1db150c3c8e664500
41 lines
1.1 KiB
JSON
41 lines
1.1 KiB
JSON
{
|
|
"name": "ReactNativeFlipperExample",
|
|
"version": "0.0.1",
|
|
"private": true,
|
|
"scripts": {
|
|
"android": "relative-deps && react-native run-android",
|
|
"ios": "relative-deps && react-native run-ios",
|
|
"start": "relative-deps && react-native start",
|
|
"prepare": "relative-deps && cd android && ./gradlew clean && cd ../ios && pod install",
|
|
"test": "jest"
|
|
},
|
|
"dependencies": {
|
|
"react": "^17.0.1",
|
|
"react-native": "^0.64.2",
|
|
"react-native-flipper": "^0.95.0"
|
|
},
|
|
"devDependencies": {
|
|
"@babel/core": "^7.14.6",
|
|
"@babel/runtime": "^7.14.6",
|
|
"babel-jest": "^27.0.2",
|
|
"jest": "^27.0.6",
|
|
"metro-react-native-babel-preset": "^0.66.0",
|
|
"react-test-renderer": "17.0.1",
|
|
"relative-deps": "^1.0.7"
|
|
},
|
|
"jest": {
|
|
"preset": "react-native"
|
|
},
|
|
"relativeDependencies": {
|
|
"react-native-flipper": "../react-native-flipper"
|
|
},
|
|
"resolutions": {
|
|
"xmldom": "0.5.0",
|
|
"react-devtools-core": "4.13.2",
|
|
"lodash": "4.17.21",
|
|
"hosted-git-info": "3.0.8",
|
|
"browserslist": "^4.16.5",
|
|
"glob-parent": "5.1.2"
|
|
}
|
|
}
|