Bug description:
figwheel-bridge tracks the js file evaluation and when /env/<platform>/main.js script is evaluated it means that all app code is loaded and can be started. But in case user code contains custom namespace called *.main, then figwheel-bridge interpret the evaluation of this namespace incorrectly and tries to start app too early.
- do not use AppRegistry.registerRunnable for mounting component to id 1, this prevents warning to be shown in yellow box. Instead use AppRegistry.registerComponent
- shim some document functions so that enabled figwheel heads-up-display works without errors and logs warnings to console (that will be shown on screen in yellow box)
- figwheel splash component now loads real app and renders root component. That has to be done to avoid using AppRegistry.registerRunnable to render real app
- new CLI command use-component <name> which save name in .re-natal config for later use in use-figwheel command
- use-figwheel now generates a map of cached 'require' calls
- figwheel-bridge.js shims require function to lookup for components by name falls back to original if nothing found
- Removed REPL based on ambly for now, need to find a good solution for both iOS and Android
- Added figwheel based on great work found in https://github.com/decker405/figwheel-react-native
- Android still does not work with figwheel, but reload works very fast
Artur Girenko