Reactjs “反应VR”;jest haste map:@providesModule命名冲突”;
我正在使用React VR命令行界面版本0.3.0。我通过软件包管理器下载了react vr。在DemoApp文件夹中运行“npm start”命令时,出现以下错误:Reactjs “反应VR”;jest haste map:@providesModule命名冲突”;,reactjs,react-360,Reactjs,React 360,我正在使用React VR命令行界面版本0.3.0。我通过软件包管理器下载了react vr。在DemoApp文件夹中运行“npm start”命令时,出现以下错误: Loading dependency graph... React packager ready. jest-haste-map: @providesModule naming collision: Duplicate module name: View Paths: /Users/akh/DemoApp/node_mo
Loading dependency graph...
React packager ready.
jest-haste-map: @providesModule naming collision:
Duplicate module name: View
Paths: /Users/akh/DemoApp/node_modules/react-vr/Libraries/Components/View/View.vr.js collides with /Users/akh/DemoApp/node_modules/react-native/Libraries/Components/View/View.js
This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
Duplicate module name: LayoutPropTypes
Paths: /Users/akh/DemoApp/node_modules/react-vr/Libraries/StyleSheet/LayoutPropTypes.vr.js collides with /Users/akh/DemoApp/node_modules/react-native/Libraries/StyleSheet/LayoutPropTypes.js
This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
Duplicate module name: AnimatedImplementation
Paths: /Users/akh/DemoApp/node_modules/react-vr/Libraries/VRReactOverrides/AnimatedImplementation.vr.js collides with /Users/akh/DemoApp/node_modules/react-native/Libraries/Animated/src/AnimatedImplementation.js
This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
Duplicate module name: NetworkOverlay
Paths: /Users/akh/DemoApp/node_modules/react-vr/Libraries/VRReactOverrides/NetworkOverlay.vr.js collides with /Users/akh/DemoApp/node_modules/react-native/Libraries/Inspector/NetworkOverlay.js
这是一个bug吗?尝试卸载,然后重新安装“react native router flux”,这对我来说很有用 npm-rm-react本地路由器流量;npm安装--保存 反应本机路由器流量
答案是:React VR团队似乎意识到了这个问题,并承诺在即将发布的版本中进行修复,请参阅此Github问题。