drapanjanas / re-natal Goto Github PK

Hi, thanks for the great framework,

I read all the document and start to use it with figwheel, but there is some problem and now I want to have a try with the original hot-Reloading Module. But after use re-natal use-figwheel, how to disable it to the init state? It will be nice if you can include this in the README.

Example app with this problem https://github.com/gphilipp/game-log/tree/89bbc99f31acf9cdbdc5289dcf04a24a2b27c5fc

Tried reinstalling and following all install / run steps correctly.

Noticed that when you do an android build like lein fighweel android there are ios dependencies in target/android/cljs_deps.js
Android build should not contain any iOS namespaces and vice-versa.

Looks like this is related to the env/* sources part.

Hi,

Thanks for create such a convenient library for mobile app developing!

I just import the react-native-vector-icons/FontAwesome today, and I tried it in iOS, it works perfectly, after I tried it in Android, it did not work, said the import is nil, the iOS and Android platform share almost the same code, and they have not met such problem before. I followed carefully the import guide, so I guess it is the import question here.

I have write it into .re-natal and the import code is like

       (def icons (r/adapt-react-class (js/require "react-native-vector-icons/FontAwesome")))

I also following the steps to import font to Android and iOS, due to the assert failed error hint, I believe I did the right so I come to re-natal here.

Hanwen

...but works just fine when the JS is compiled+delivered via Figwheel/React Native packager.

Screenshot:

...and Xcode console log:

2016-03-27 01:37:02.578 [error][tid:com.facebook.React.JavaScript] Can't find variable: React
2016-03-27 01:37:02.587 [fatal][tid:com.facebook.React.RCTExceptionsManagerQueue] Unhandled JS Exception: Can't find variable: React
2016-03-27 01:37:02.813 [error][tid:com.facebook.React.JavaScript] Module AppRegistry is not a registered callable module.
2016-03-27 01:37:02.817 [fatal][tid:com.facebook.React.RCTExceptionsManagerQueue] Unhandled JS Exception: Module AppRegistry is not a registered callable module.
2016-03-27 01:37:03.840 [warn][tid:com.facebook.React.JavaScript] Unable to load source map: No source map URL found. May be running from bundled file.
2016-03-27 01:37:03.841 [warn][tid:com.facebook.React.JavaScript] Unable to load source map: No source map URL found. May be running from bundled file.

I'm attaching the main.jsbundle:
main.jsbundle.zip

A readable one can be created with:

node --max-old-space-size=4096 node_modules/react-native/local-cli/cli.js bundle --entry-file index.ios.js --platform ios --dev true --bundle-output "ios/main.jsbundle"

Steps to reproduce:

npm install -g re-natal
re-natal init CrashingApp
cd crashing-app
re-natal xcode
lein prod-build

Make sure the JS is delivered from a bundle by editing ios/CrashingApp/AppDelegate.m, commenting this line:

 // jsCodeLocation = [NSURL URLWithString:@"http://localhost:8081/index.ios.bundle?platform=ios&dev=true"];

and uncommenting this one:

   jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];

Connect device, select it as launch destination in Xcode and hit the run button (after the prod-build process in step 1 is complete).

Expected: app launches after a brief display of a "loading from bundle" status message.
Observed: App crashes with aforementioned exception.

The app works fine on a device and in the simulator when run with:

lein figwheel ios
npm start

(+ reverse step 2 above to disable the bundle).

re-natal version is 0.2.28.

This issue seems like it might be related:
este/este#752

My guess is that the JS compiled with ":optimizations :simple" (as in the default config of the prod-build profile) somehow trips up some optimization/transformation the react native packager does to the JS when creating a bundle.

I tried switching the prod-build leiningen profile to :optimizations :none (as in the working figwheel profile configuration), but then the bundle cannot be created at all, the process dying with the following message:

uncaught error Error: UnableToResolveError: Unable to resolve module env.ios.main from /Users/gnl/Documents/cljs-issue/testcases/test-four/index.ios.js: Unable to find this module in its module map or any of the node_modules directories under /Users/node_modules/env.ios.main and its parent directories

Either way, this should work with the default configuration, as it most definitely used to. I'm not quite sure when it stopped, since I was happily developing with Figwheel for more than a week until I tried creating a standalone package to deploy to a device and saw this happen.

Oddly enough, even when downgrading re-natal to 0.2.26 (which I'm pretty sure I used for my last successful packaging) and init-ing a new default project I observe the same behaviour, so not sure which part of the build chain is causing this exactly.

In the same environment, creating a standard RN project with react-native init DemoApp and running on a device from a JS bundle works just fine.

Can anyone else reproduce this?

Thanks!

Currently there is no easy to set the figwheel websocket url to anything other than 'ws://localhost:3449' which would be very helpful for live code reloading on an iOS device.

I tried changing the :websocket-url in env/dev/env/ios/main.cljs, but the localhost URL still ends up in:

ios/figwheel/connect.cljs
target/ios/figwheel/connect.cljs

I'm not familiar enough with the code base/figwheel/compilation process and wasn't able to find a quick solution. Help! :)

P.S. Awesome project!

Hi,

I tried to run re-natal init SomeApp on W7 and it fails with:

Leiningen is required (http://leiningen.org)

As you suggested in slack the problem is that type does not exist on windows.

reagent6, iOS, Mac

TLDR: Some RN errors are not reported anywhere

All of a sudden the hot code reload fails and no more changes are pushed. That usually means that I screwed something up. If I reload the emulator I just get Waiting for Figwheel to load files. The figwheel REPL shows nothing and a (reset-autobuild) successfully recompiles the project.

It is like these issues fall between compile issues shown by figwheel and the red screen of RN. I have not got around to make an MWE but an example issue is when I accidentally ran the function r/adapt-react-class twice on an object.

Not sure if this issue is related to re-natal but I never experienced them in React Web.

Hi,

This is an awesome tool that you have here and currently on the list of suggested topics to the Clojure/West conference ClojureScript + ReactNative is wining, people are interested in this.

We should spread the news about ClojureScript and React Native. Currently there are not that much videos exists about this topics and I'm almost sure that many folks from JS community would be crazy to see REPL support (unique feature for ClojureScript) and macroses I'm sure would blow their mind! :)

Anyone experience slow bootup times on Android using this stack? Seems like a 1-2s lag before the JS part of the app kicks in.

Hey there! Thanks so much for such a cool project :) I've been looking to try out ClojureScript and Reagent/Re-frame on a fun project, and this seemed like a great way to try.

However, I noticed when the app runs in Dev mode (haven't tried production), it takes up a great deal of memory and after a few reloads causes the app in my Android emulator to crash. (Note: I tried both the default Android Emulator and Genymotion).

Not sure if anyone has ideas on the source of this problem or how easy it would be to fix up, but this looked like a bit of a show-stopper for a first time user. Thanks again for all the time and effort on this project!

Steps:

1. Follow the instructions to get the app running on Android
2. Reload the android app several times (opening the menu, "Reload JS")
3. App will crash (adb log shows an Out Of Memory Trend)

Looking at the monitor, there's a ton of memory usage from the sample app. Here's a comparison of the default re-natal memory usage vs react-native memory usage:

Stock React Native Project: Memory Usage

The blips in the graph come from reloading. Notice it always stays around 3mb of memory usage.

The increases come after every time I reload the project. Notice the memory continues to grow and grow:

Eventually resulting in this Out Of Memory Crash:

--------- beginning of crash
01-10 13:50:00.885 19749-21983/com.gol E/AndroidRuntime: FATAL EXCEPTION: OkHttp Dispatcher
                                                         Process: com.gol, PID: 19749
                                                         java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack trace available
01-10 13:50:00.892 19749-19757/com.gol E/System: java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack trace available

                                                 [ 01-10 13:50:00.895  1362: 1835 D/         ]
                                                 HostConnection::get() New Host Connection established 0xa07b7340, tid 1835
01-10 13:50:00.911 19749-19749/com.gol I/art: Clamp target GC heap from 67MB to 64MB

In the README documentation, it is mentionned that
You have to reload your app, and should see the REPL coming up with the prompt.

Does this mean to reload the entire application ? On a real Android device, the only way I've managed to have a REPL prompt was to go to "debug js" to launch a chrome instance on the computer, but I'm not sure it's the proper way to do it.

Thanks ;)

Hi. Would you take a PR for a command that just calls copyFigwheelBridge() with name from the config? We'd like to pull in the great upstream work you're doing on figwheel-bridge.js. doUpgrade() doesn't work for us because we have a different project layout than env/ and "src/#{projNameUs}/ios/core.cljs" and we're not looking to use the other changes e.g. patch react-native. Cheers

I think figwheel-bridge.js has a regression:

function compileWarningsToYellowBox() {
    var log = window.console.log;
    var compileWarningRx = /Figwheel: Compile Warning/;
    window.console.log = function (msg) {
        if (msg.match(compileWarningRx) != null) {
            console.warn(msg);
        } else {
            log.call(window.console, msg);
        }
    };
}

This function assumes that msg is a string (it can also be a javascript/cljs object) and silently fails when match is called and it's not a string. Below is a fix. Also, I recommend just matching on "Figwheel Compile" as there are also "Figwheel Compile Exception"s.

function compileWarningsToYellowBox() {
    var log = window.console.log;
    var compileWarningRx = /Figwheel: Compile/;
    window.console.log = function (msg) {
        if (typeof msg.match === 'function' && msg.match(compileWarningRx) != null) {
            console.warn(msg);
        } else {
            log.call(window.console, msg);
        }
    };
}

So, I tried forking your repo and doing a pull request, but the forked repo was "natal". Now I'm certainly no github genius, but I think this is problematic.

Also, great work on the rewrite! Firebase is working out of the box now. :)

In the future-app sample application, how come there are two core.cljs files (for both android and ios) ? Shouldn't there be only one base code for all platforms ?

Thanks ;)

Hi. While taking a look at luno-react-native I had the above error.

Steps to reproduce:

1. git clone luno-react-native to alwx/luno-react-native@122d541
2. re-natal upgrade

The failure seems to be coming from editing a non-existing file on older projects. This can be fixed by putting a file exists check before that line is invoked. Since that fn is called by multiple contexts, we may need to pass a boolean to patchReactNativePackager to check whether the file exists or not. Happy to submit a PR if you explain the approach you want.

For this particular case it would've been helpful if there was a stacktrace. Setting this event may help with that

Thanks for re-natal and look forward to using it more!

I just got back to working on #37 and started noticing some weird rendering issues and glitches. Specifically:

• rendering refreshes very slowly, and
• the alert OK button isn't clickable

I was able to localize it to the iOS 9.1 simulator on my machine. 8.1 works no problem. I've not tried a physical device.

I've include a screen capture of what I am seeing. Am I the only one? I doubt it's re-natal specific. Thanks for the sanity check.

I'm facing an annoying issue with WebViews.
When using figwheel, each time I save (and thus hot reload the app) all webviews in my app are "refreshed".
It's not the case when using JavaScript react native projects with Hot Reload enabled. The UI tree is updated, and WebViews are not reloading their pages.

re-natal + figwheel + save = web view is refreshing
vanilla react native + hot reload + save = web view is not refreshing

I played around with a google maps examples.

"adb reverse" - is not available for android version prior to 5.0. So, I cannot use to reverse-forward port 3449 from android localhost to my Dev machine.
Need a way to specify IP to use by figwheel

First - happy new year! Thanks for this project!

My apologies if the answer is obvious. We have a project where we plan to have iOS and Android code co-exist in the same repository instead of have a single repo for each.

How should we approach having a unified codebase if the host is changed for iOS and shared code when use-figwheel -H is used when configuring it for android?

As noted in readme to support source maps, RN packagers is patched in local node_module. Which is a small but dirty hack. It should be totally harmless, but still, soap and water can not wash off the dirt from my hands :)

So here's the plan:

1. Implement an new option for packager to force serving files matching the provided pattern from the file system.
2. Implement persistent configuration for being able to persist the packager options without need of supplying them in command line. Command line arguments should override those in config

I would like to ask whether it would be possible to work on Android (no XCode installed) and Linux.

If no, which I can already see when I do re-natal init myApp, what could be done to contribute this feature? Is it a lot of work?

Thanks and very good job!

Currently, when using figwheel CLJS compilation erros are almost invisible. Same as other errors like if you mistyped some property name: instead of :font-weight you accidently typed :font-weihgt such error stays not visible.
If you use React Native without CLJS and figwheel you would see warnings in yellow box at the bottom of simulator screen.

Would you be interested in a PR to change schema in cljs-reagent6 for cljs.spec? This will require upgrading the template to use latest clojurescript and a clojure 1.8.0-alpha version. I've been using cljs.spec in deployed ios + android re-natal apps and it's been working great :)

As the essay of the lisp curse predicts we already have some fragmentation in the very young CLJS RN space: re-natal vs boot-react-native. re-natal is clearly the most popular one if you judge from number of stars and forks here on GitHub. I am pretty sure that as RN usage grows in the CLJS community people are going to want to use boot since it seems to be very popular for the web/node. While the fragmentation between boot and lein are reasonable since they represent different philosophies I do not feel the same is true for re-natal vs boot-react-native and therefore I'd like to raise the question if these projects could be merged or that re-natal would add boot to the roadmap.

Currently there is a macro env.require-img/require-img which expands to {:uri "http://localhost:8081/path/to/image.png"} during development and to (js/require "./path/to/image.png) during prod build.
This was more like a workaround just to support Static Image Resources in re-natal.
Now this macro can be deprecated/removed in favour of using similar approach like was implemented for #5

Implementation could be smth like:

• in use-figwheel scan images directory and statically include them same as with use-component
• add CLI command to include other directories with images

Pros

• normal js/require can be used to require a static image

Cons

• when new image is added, need to call use-figwheel again and reload app via "Reload JS"

Currently there is Reagent specific code in env/dev/*/main.cljs. Regenerating these files makes it impossible to use om-next.
To support Android simulators, re-natal might just update fighweel url to set simulator specific IP address instead of regenerating whole file.
Actually, there is no need to change host for iOS at all. Only for android host might be localhost, 10.0.2.2 or 10.0.3.2.
Probably need to create dedicated command for changing host only for android and remove this concern from use-figwheel.

Hi
I've been trying to use react-native-vector-icons in my re-natal generated project. But for some reason I keep on ending up with the requiring unknown module error.

I've tried requiring the module using the following different paths below:
(def icon (js/require "react-native-vector-icons/FontAwesome.js"))
(def icon (js/require "react-native-vector-icons/FontAwesome"))
(def icon (js/require "FontAwesome.js"))
It seems to happen with other custom react native components as well. So it seems maybe I'm doing something wrong

Hey!

Thanks for this great project. I adapted the code to use in https://exponentjs.com/ (allows you to publish react-native apps for browsing on both ios and android). Everything works: code reload, repl, cider integration with autocomplete, docs. The use case was a little different (ios and android have common code) so I just adapted the code. Here's a gif: https://twitter.com/snikhilesh/status/722743659674804224

I made it automatically write the development environment ip to a javascript module 'dev-env' that goes in target/ so that env.main can read that to pass to figwheel/watch-and-reload. You may want to adapt your code to do this too. Here is the relevant change:
expo/exp-cljstest@e762b4d

I would've done a pull request but I only wrote the case for reagent and my directory structure is a bit different because I don't have separate ios and android code.

We may be able to do it without writing a .js file and instead a .cljs file that writes to a new dev.config namespace or something (will figwheel automatically load a new .cljs file added under target/?). Let me know if you go down that route, I'd like to see what you come up with!

We could also just use closure defines in project.clj to inject constants into the resultant JS--haven't explored that route yet.

Problems with Firebase related to this were reported on slack channel. There might more libs which might be 'fooled' by existing window.document object and work not properly in RN environment.

The solution is to make Figwheel 'think' that it is Node.js environment rather than browser.

I don't know if this is known, but:

• start new project via re-natal init
• re-natal use-android-device genymotion
• re-natal use-figwheel
• start figwheel as (start-figwheel "ios" "android")
• start IOS simulator, genymotion

Now when u make file change, figwheel pushes new code twice. I mean twice into IOS, twice into android. If I hadn't start e.g. genymotion, IOS would be notified of file change just once - correctly.
As you can see in the picture, code is run twice on IOS after single file change.

The solution I came up with: Start running 2 figwheels on different ports, Android would connect to one, IOS to the other one. Everything works as expected. Code is pushed just once.

My user.clj looks like:

(ns user
  (:require [figwheel-sidecar.repl-api :as ra]
            [figwheel-sidecar.system :as fs]))
;; This namespace is loaded automatically by nREPL

;; read project.clj to get build configs
(def profiles (->> "project.clj"
                   slurp
                   read-string
                   (drop-while #(not= % :profiles))
                   (apply hash-map)
                   :profiles))

(def cljs-builds (get-in profiles [:dev :cljsbuild :builds]))

(defn start-figwheel
  ([build-id] (start-figwheel build-id false))
  ([build-id repl?]
   (let [port (if (= build-id :android) 6551 6552)
         start-fig (if repl? ra/start-figwheel! fs/start-figwheel!)]
     (start-fig
       {:figwheel-options {:server-port port}
        :build-ids        [build-id]
        :all-builds       cljs-builds}))
   (when repl?
     (ra/cljs-repl))))

(defn start-figwheels []
  (start-figwheel :android)
  (start-figwheel :ios true))

And we can't forget to change :websocket-url in env.android.main and env.ios.main to ports 6551 and 6552

I could run the following command successfully, but "lein figwheel android" runs forever, the last message is "Prompt will show when Figwheel connects to your application". What's wrong?

oracle@SomeHost /data/node-v4.4.3/bin/future-app $ re-natal use-android-device avd
Using host '10.0.2.2' for android device type 'avd'

oracle@SomeHost /data/node-v4.4.3/bin/future-app $ re-natal use-figwheel
Cleaning...
index.ios.js was regenerated
index.android.js was regenerated
AppDelegate.m was updated
Dev server host for iOS: localhost
Dev server host for Android: 10.0.2.2

oracle@SomeHost /data/node-v4.4.3/bin/future-app $ adb devices
List of devices attached
R32D100AT3K device

oracle@SomeHost /data/node-v4.4.3/bin/future-app $ lein figwheel android
Figwheel: Starting server at http://localhost:3449
Port 3449 is already being used. Are you running another Figwheel instance? If you want to run two Figwheel instances add a new :server-port (i.e. :server-port 3450) to Figwheel's config options in your project.clj
Figwheel: Watching build - android
Compiling "target/android/not-used.js" from ["src" "env/dev"]...
Successfully compiled "target/android/not-used.js" in 2.637 seconds.
Launching ClojureScript REPL for build: android
Figwheel Controls:
(stop-autobuild) ;; stops Figwheel autobuilder
(start-autobuild [id ...]) ;; starts autobuilder focused on optional ids
(switch-to-build id ...) ;; switches autobuilder to different build
(reset-autobuild) ;; stops, cleans, and starts autobuilder
(reload-config) ;; reloads build config and resets autobuild
(build-once [id ...]) ;; builds source one time
(clean-builds [id ..]) ;; deletes compiled cljs target files
(print-config [id ...]) ;; prints out build configurations
(fig-status) ;; displays current state of system
Switch REPL build focus:
:cljs/quit ;; allows you to switch REPL to another build
Docs: (doc function-name-here)
Exit: Control+C or :cljs/quit
Results: Stored in vars *1, *2, *3, *e holds last exception object
Prompt will show when Figwheel connects to your application

Setting the compiler option in project.clj

:closure-defines {my.ns.var true}

does not work (due to the statement being compiled to not-used-js).

I also tried to set it in figwheel-bridge.js like this:

var CLOSURE_UNCOMPILED_DEFINES = {"my.ns.var":true};

But it didn't work either.

Any ideas on how to get it working?

Hi, I'm trying to get started with re-natal. I have the sample project running, and I'm about to make my first component / sub-view. The generated project doesn't have an example sub-component, and when I try to make one according to the reagent docs, it fails.

If I try to move the press-me button into a component:

(defn press-me-label [name]
  [text {:style {:color "white" :text-align "center" :font-weight "bold"}} (str "press me: " name)])

Then I can call it as a function as follows:

       ...
       [touchable-highlight {:style {:background-color "#999" :padding 10 :border-radius 5}
                             :on-press #(alert "HELLO!")}
        (press-me-label "bob")]])))

But the reagent docs specifically say you're supposed to call it as a vector:

       ...
       [touchable-highlight {:style {:background-color "#999" :padding 10 :border-radius 5}
                             :on-press #(alert "HELLO!")}
        [press-me-label "bob"]]])))

However, when I do that I get the following error:

Am I doing something wrong? If creating components differs from reagent, can you specify in the documentation how to do so? I've trying using a Form-2 component and it still doesn't work. Am I supposed to use the function syntax? why? What if I need a component that requires setup?

I am trying to initialize new project but it stops during Creating React Native skeleton.
I wait about one hour but it did not work.
I also tried using http_proxy

Is there anyway see the what is happening behind?
As I checked there is a --verbose option in natal but not in re-natal

react-native version 0.18.x is dependent on react 0.14.x while reagent 0.5.x is dependent on react 0.13.x.

These are the breaking changes for react 0.14.0

Not sure if this is really an issue but its worth highlighting.

Similarily how it is done in original Natal init command.

Open points:

1. Need to figure out suitable om-next architecture for crossplatform apps to reuse common code. Only UI part should be separate.
2. What component wrappers to use for om-next? Reagent has function adapt-react-class, but in om-next examples usually use some wrapper library like natal-shell or ktoa has smth similar. Maybe better not to use any by default and let the developer decide?

This is a good excerse to learn om-next basics, so will it take some time. Any proposals on this topic are wellcome.

I tried creating a new project with re-natal 0.2.13 and was unable to start the app due to an "importScript not defined" error.

It was fixed by upgrading react-native-cli to the latest version, 1.9. Please add this as a dependency in the README to save other people time! :)

The README keeps telling us that we might need to restart the packager for the REPL to connect. How do we do that? It would be cool to include that in the README as well.

My REPL won't connect to my app, and I want to try this step but don't know how to proceed.

I got re-natal, and ran re-natal init:

$ re-natal init FutureApp
Creating FutureApp

Creating Leiningen project
Updating Leiningen project
Creating React Native skeleton. Relax, this takes a while...
Creating Re-Natal config
Compiling ClojureScript

To get started with your new app, first cd into its directory:
cd future-app

Open iOS app in xcode and run it:
re-natal xcode

To use figwheel start "Debug in Chrome" in simulator and type:
re-natal use-figwheel
lein figwheel ios

Reload the app in simulator

At the REPL prompt type this:
(in-ns 'future-app.ios.core)

Changes you make via the REPL or by changing your .cljs files should appear live.

Try this command as an example:
(dispatch [:set-greeting "Hello Native World!"])

✔ Done

I then ran re-natal xcode and re-natal use-figwheel, and got an error on the third step

$ lein figwheel ios
clojure.lang.Compiler$CompilerException: java.io.FileNotFoundException: Could not locate cljs/analyzer__init.class or cljs/analyzer.clj on classpath: , compiling:(figwheel_sidecar/utils.clj:1:1)
 at clojure.lang.Compiler.load (Compiler.java:7142)
    clojure.lang.RT.loadResourceScript (RT.java:370)
    clojure.lang.RT.loadResourceScript (RT.java:361)
    clojure.lang.RT.load (RT.java:440)
    clojure.lang.RT.load (RT.java:411)
    clojure.core$load$fn__5066.invoke (core.clj:5641)
    clojure.core$load.doInvoke (core.clj:5640)
    clojure.lang.RestFn.invoke (RestFn.java:408)
    clojure.core$load_one.invoke (core.clj:5446)
    clojure.core$load_lib$fn__5015.invoke (core.clj:5486)
    clojure.core$load_lib.doInvoke (core.clj:5485)
    clojure.lang.RestFn.applyTo (RestFn.java:142)
    clojure.core$apply.invoke (core.clj:626)
    clojure.core$load_libs.doInvoke (core.clj:5524)
    clojure.lang.RestFn.applyTo (RestFn.java:137)
    clojure.core$apply.invoke (core.clj:626)
    clojure.core$require.doInvoke (core.clj:5607)
    clojure.lang.RestFn.invoke (RestFn.java:551)
    figwheel_sidecar.config$eval2752$loading__4958__auto____2753.invoke (config.clj:1)

This is my first time posting an issue on Github, so hope I don't screw this up haha!

Just tried updating both my Clojure and ClojureScript dependencies in the project.clj of my new app project. Upgrading to the latest CLJS version 1.9.227 worked fine. When trying to go up from Clojure 1.9.0-alpha10 to 1.9.0-alpha11, I get the following massive error message:

Exception in thread "main" java.lang.IllegalArgumentException: Call to clojure.core/ns did not conform to spec:
In: [3 0] val: import fails spec: :clojure.core.specs/ns-refer-clojure at: [:args :clauses :refer-clojure :clause] predicate: #{:refer-clojure}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-require at: [:args :clauses :require :clause] predicate: #{:require}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-import at: [:args :clauses :import :clause] predicate: #{:import}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-use at: [:args :clauses :use :clause] predicate: #{:use}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-refer at: [:args :clauses :refer :clause] predicate: #{:refer}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-load at: [:args :clauses :load :clause] predicate: #{:load}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-gen-class at: [:args :clauses :gen-class :clause] predicate: #{:gen-class}
:clojure.spec/args  (cljsbuild.crossover (:use [clojure.java.io :only [as-url resource]]) (:require [cljsbuild.util :as util] [clojure.string :as string] [fs.core :as fs]) (import java.io.File java.net.URLDecoder))
, compiling:(cljsbuild/crossover.clj:1:1)
    at clojure.lang.Compiler.macroexpand1(Compiler.java:6795)
    at clojure.lang.Compiler.macroexpand(Compiler.java:6861)
    at clojure.lang.Compiler.eval(Compiler.java:6935)
    at clojure.lang.Compiler.load(Compiler.java:7403)
    at clojure.lang.RT.loadResourceScript(RT.java:374)
    at clojure.lang.RT.loadResourceScript(RT.java:365)
    at clojure.lang.RT.load(RT.java:455)
    at clojure.lang.RT.load(RT.java:421)
    at clojure.core$load$fn__7645.invoke(core.clj:6008)
    at clojure.core$load.invokeStatic(core.clj:6007)
    at clojure.core$load.doInvoke(core.clj:5991)
    at clojure.lang.RestFn.invoke(RestFn.java:408)
    at clojure.core$load_one.invokeStatic(core.clj:5812)
    at clojure.core$load_one.invoke(core.clj:5807)
    at clojure.core$load_lib$fn__7590.invoke(core.clj:5852)
    at clojure.core$load_lib.invokeStatic(core.clj:5851)
    at clojure.core$load_lib.doInvoke(core.clj:5832)
    at clojure.lang.RestFn.applyTo(RestFn.java:142)
    at clojure.core$apply.invokeStatic(core.clj:659)
    at clojure.core$load_libs.invokeStatic(core.clj:5889)
    at clojure.core$load_libs.doInvoke(core.clj:5873)
    at clojure.lang.RestFn.applyTo(RestFn.java:137)
    at clojure.core$apply.invokeStatic(core.clj:659)
    at clojure.core$require.invokeStatic(core.clj:5911)
    at clojure.core$require.doInvoke(core.clj:5911)
    at clojure.lang.RestFn.invoke(RestFn.java:436)
    at user$eval15.invokeStatic(form-init2469899088480641630.clj:1)
    at user$eval15.invoke(form-init2469899088480641630.clj:1)
    at clojure.lang.Compiler.eval(Compiler.java:6951)
    at clojure.lang.Compiler.eval(Compiler.java:6940)
    at clojure.lang.Compiler.load(Compiler.java:7403)
    at clojure.lang.Compiler.loadFile(Compiler.java:7341)
    at clojure.main$load_script.invokeStatic(main.clj:276)
    at clojure.main$init_opt.invokeStatic(main.clj:278)
    at clojure.main$init_opt.invoke(main.clj:278)
    at clojure.main$initialize.invokeStatic(main.clj:309)
    at clojure.main$null_opt.invokeStatic(main.clj:343)
    at clojure.main$null_opt.invoke(main.clj:340)
    at clojure.main$main.invokeStatic(main.clj:422)
    at clojure.main$main.doInvoke(main.clj:385)
    at clojure.lang.RestFn.applyTo(RestFn.java:137)
    at clojure.lang.Var.applyTo(Var.java:700)
    at clojure.main.main(main.java:37)
Caused by: java.lang.IllegalArgumentException: Call to clojure.core/ns did not conform to spec:
In: [3 0] val: import fails spec: :clojure.core.specs/ns-refer-clojure at: [:args :clauses :refer-clojure :clause] predicate: #{:refer-clojure}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-require at: [:args :clauses :require :clause] predicate: #{:require}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-import at: [:args :clauses :import :clause] predicate: #{:import}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-use at: [:args :clauses :use :clause] predicate: #{:use}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-refer at: [:args :clauses :refer :clause] predicate: #{:refer}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-load at: [:args :clauses :load :clause] predicate: #{:load}
In: [3 0] val: import fails spec: :clojure.core.specs/ns-gen-class at: [:args :clauses :gen-class :clause] predicate: #{:gen-class}
:clojure.spec/args  (cljsbuild.crossover (:use [clojure.java.io :only [as-url resource]]) (:require [cljsbuild.util :as util] [clojure.string :as string] [fs.core :as fs]) (import java.io.File java.net.URLDecoder))

    at clojure.spec$macroexpand_check.invokeStatic(spec.clj:627)
    at clojure.spec$macroexpand_check.invoke(spec.clj:616)
    at clojure.lang.AFn.applyToHelper(AFn.java:156)
    at clojure.lang.AFn.applyTo(AFn.java:144)
    at clojure.lang.Var.applyTo(Var.java:700)
    at clojure.lang.Compiler.macroexpand1(Compiler.java:6789)
    ... 42 more
Error encountered performing task 'cljsbuild' with profile(s): 'prod'
Subprocess failed

Obviously a lot being worked on and changed with Clojure.spec. Does anyone know specifically what change between alpha10 and alpha11 might be causing this?

Thanks!

Right now re-natal logs a lot of info to the console. It's easy to get lost in the sea of cljs packages that are loaded and evaled (two separate messages per file). Maybe removing some of the logging would help users see more signal than noise? Here's what my console looks like after I disabled some of the info logs:

Beautiful! :)

React 0.15 came out today, and removes cloneWithProps (which is still used by react-native 0.22.2).

re-natal pulls in React 0.15, but produces an error about cloneWithProps.

[email protected] still requires react@^0.14.5 to run (probably because of the breaking changes):

npm WARN [email protected] requires a peer of react@^0.14.5 but none was installed.

I tried downgrading to [email protected], but re-natal does not allow anything below [email protected], when you run re-natal use-figwheel.

Not sure what the workaround is, until React Native fixes the breaking change in React 0.15 and upgrades.

https://github.com/binaryage/dirac

Problem

The path to android and ios main.cljs is currently hardcoded to env/{dev|prod}/env/{ios|android}/main.cljs
The command re-natal use-figwheel cannot be configured to match my project structure (see My use case).

Suggestion

It would be nice to have the path to {dev|prod}/env/{ios|android}/main.cljs configurable, i.e. having dir env configurable. To put something in .re-natal like:

{
...
  "envRoot": "env",
...
}

My use case

I have a lot of platforms and mains - server, web and mobile - and I'd like to have the same structure for all my mains. Here's part of my current structure:

env/client/dev/web/main.cljs
env/client/prod/web/main.cljs
env/client/dev/ios/main.cljs
env/client/prod/ios/main.cljs
env/client/dev/android/main.cljs
...
env/common/dev/utils.cljc
...
env/server/dev/server/main.clj
env/server/dev/server/repl.clj
...

In my case, I'd configure .re-natal: "envRoot": "env/client"

I'm trying to use an android emulator with re-natal, but the command
re-natal use-android-device avd

raised the following error in the console :
unknown command use-android-device. See re-natal --help for valid commands

Using re-natal 0.2.18 on Arch Linux.

Is this command supported on Linux ?

I hit this problem when running app after lein prod-build
A workaround for this problem can be found here: facebook/react-native#8475

Until permanent fix, you have to downgrade to [email protected]

Did:

• Called apply js/console.log with many arguments.

Expected:

• To see all arguments logged in my console.

Happened:

• Saw only the first argument being logged.

Suggested solution:
Call log with apply with all arguments:

// figwheel-bridge.js

    window.console.log = function (msg) {
        if (compileWarningRx.test(msg)) {
            console.warn(msg);
        } else {
            log.apply(window.console, arguments);
        }
    };

Currently version:

// figwheel-bridge.js

    window.console.log = function (msg) {
        if (compileWarningRx.test(msg)) {
            console.warn(msg);
        } else {
            log.call(window.console, msg);
        }
    };

I am interested in supporting Rum https://github.com/tonsky/rum for react-native development through re-natal.

Rum is a minimal Clojure wrapper around React that is opinion-less.

I took an initial stab at getting it to work but I was having trouble with sablono https://github.com/r0man/sablono (it seems tightly coupled with browser DOM stuff).

Shimming a couple things and writing some custom Rum macros and mixins to not use sablono should be all that it takes.

Putting this out there if anyone else is interested as well and/or has insights.