Paulus Esterhazy

@theronic I'm not @vikeri, but I'm using re-natal these days, which IMO is based on the better approach (using figwheel for much of the work). Boot-react-native needs significant work to...

@theronic, briefly: Re-natal has the better approach. It serves, via RN packager, only a small stub, including only pointers JS deps and the figwheel bridge. All the rest is done...

Unfortunately I don't have time to update boot-react-native anymore. Re-natal works much better than boot-react-native these days and is actively maintained, so my suggestion would be to look into that.

Do you know which part of the shim causes these issues? - window.localStorage - window.document - window.location ? What kind of issue are you seeing? I'm not sure if these...

After looking into this, it looks like boot-reload needs a small patch to work without window.location being present. I've submitted a PR: https://github.com/adzerk-oss/boot-reload/pull/110 Not seeing any other issues removing fakeLocalStorageAndDocument...

Also disabled sourcemap support in `setup-links-for-dependency-map`. The step of adding sourcemaps caused `boot` to recognize all files as changed (because of updated mtimes). For details, see https://github.com/mjmeintjes/boot-react-native/issues/57 To re-enable sourcemaps,...

Idea: when putting it back in, hide sourcemaps behind a feature flag so we can turn it off if it breaks things

In the same vein, `Writing cljs-template to shim_browser_repl_bootstrap.cljs` and the like are not actually interesting to user. Plus it's not a place that is likely to break. How about using...

Removing the reference to the "setState" warning, which does not show up anymore in latest master. "Unbalanced calls" still occurs though

@hugoduncan, interesting. Any idea what might be the cause of this? I'd like to aim for a "0 warning" situation.