Ignite: No bundle URL present - @providesModule collision - react-native-router-flux

Created on 20 Apr 2017  ยท  4Comments  ยท  Source: infinitered/ignite

So I tried spinning up an Ignite app and got this:

Last login: Thu Apr 20 09:24:24 on ttys004
/Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native/packager/launchPackager.command ; exit;
โžœ  ~  /Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native/packager/launchPackager.command ; exit;
~/Code/ReactNative/apps/Xbow/node_modules/react-native/packager ~
Scanning 827 folders for symlinks in /Users/jh/Code/ReactNative/apps/Xbow/node_modules (5ms)
 โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” 
 โ”‚  Running packager on port 8081.                                            โ”‚ 
 โ”‚                                                                            โ”‚ 
 โ”‚  Keep this packager running while developing on any JS projects. Feel      โ”‚ 
 โ”‚  free to close this tab and run your own packager instance if you          โ”‚ 
 โ”‚  prefer.                                                                   โ”‚ 
 โ”‚                                                                            โ”‚ 
 โ”‚  https://github.com/facebook/react-native                                  โ”‚ 
 โ”‚                                                                            โ”‚ 
 โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ 
Looking for JS files in
   /Users/jh/Code/ReactNative/apps/Xbow 

Loading dependency graph...
React packager ready.

jest-haste-map: @providesModule naming collision:
  Duplicate module name: react-native
  Paths: /Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native/package.json collides with /Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native-router-flux/node_modules/react-native/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
Failed to build DependencyGraph: @providesModule naming collision:
  Duplicate module name: react-native-vector-icons
  Paths: /Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native/local-cli/core/__fixtures__/files/package.json collides with /Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native-router-flux/node_modules/react-native/local-cli/core/__fixtures__/files/package.json

This error is caused by a @providesModule declaration with the same name across two different files.
Error: @providesModule naming collision:
  Duplicate module name: react-native-vector-icons
  Paths: /Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native/local-cli/core/__fixtures__/files/package.json collides with /Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native-router-flux/node_modules/react-native/local-cli/core/__fixtures__/files/package.json

This error is caused by a @providesModule declaration with the same name across two different files.
    at HasteMap._updateHasteMap (/Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native/packager/src/node-haste/DependencyGraph/HasteMap.js:158:13)
    at p.getName.then.name (/Users/jh/Code/ReactNative/apps/Xbow/node_modules/react-native/packager/src/node-haste/DependencyGraph/HasteMap.js:133:31)
~
Process terminated. Press <enter> to close the window

This is what I've tried so far:

โ€ข Reset simulator, made sure Xcode was up to date, rm node_modules and yarn
โ€ข Ignited with no options, ignited with max options
โ€ข Used ignite from master, used ignite from npm

@skellock let me know it's a breaking change introduced by react-native-router-flux. I'm going to switch over to ignite-ir-next since that's using react-navigation.

bug critical

All 4 comments

ignite-ir-next is fine. going to pin the rnrf in our boilerplate. standby. testing.

image

This is how I fixed it. I'll update the boilerplate to lock versions so this doesn't happen anymore.

Thanks to @skellock for the help!

Sweet. Thx for the quick fix. Can you npm publish out a new version too with the fix (you might be already I haven't checked and am too lazy to stop typing this and look)?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

skellock picture skellock  ยท  3Comments

GantMan picture GantMan  ยท  3Comments

GantMan picture GantMan  ยท  3Comments

orozcojair picture orozcojair  ยท  3Comments

ta-ssi-lo picture ta-ssi-lo  ยท  3Comments