holy smokes… has anyone run into this or a variation of? https://github.com/facebook/react-native/issues/15195

I just started happening seemingly from nowhere …

can’t do a production build at the moment, veeeeery annoying…

also: on a related note - has there been any discussion that I have missed re: GETTING RID OF packager/metro-bundler/whatever

I saw some people talking about it, but lost the thread

I’m literally willing to put a few weeks of work myself to get this done… those things are beyond frustrating to use

some awesome finding https://github.com/drapanjanas/re-natal/issues/127

finally able to complete a production build in under 1-2 minutes! in 1+ year of React Native this is a first

figured out how to exclude the Google Closure output from the evil hands of metro-bundler/Babel 😂

there should be a Nobel prize in Babel hacking

Does RN affect ClojureScript's :preloads at all? I haven't been to preload anything, unfortunately.

I have a simple ns with (ns me.dev) (.log js/console "something")) and I've :preloads [me.dev] in my leiningen project, in the cljsbuild :compiler map. I see nothin'.

@raspasov That looks awesome; I'll give it a shot this week. Thanks so much for digging deeper into metro for it.

@jeaye I haven’t used :preloads myself - I’m reading the docs https://clojurescript.org/reference/compiler-options - is that something only for development? all my findings are mostly for production build (in RN there’s a difference between dev and production and you MUST compile for production otherwise your app is many times slower); luckily, I haven’t had many problems for dev builds with React Native, they have mostly worked, or at least much more so than when trying to get metro/babel to go through a few MB one file output under Google Closure :advanced (or even :simple - that might be even harder but I haven’t been using :simple or other Closure options in a while)

Yeah, the :preloads issue is entirely separate from the Babel builds and all of that other nonsense.

I brought it up a few hours ago and only now just read about your progress on the Babel issue.

:preloads is something that's only used in development and I'm looking to use it to help me trace events as they flow through re-frame. It uses preloads to hook some functions, but the preloading isn't working at all. When I've tried with a simple test ns, it also didn't work, so it might be something RN related.

right — so if it gets included in your final :advanced output such index.ios.js (or better my-unique-name.ios.js like I wrote for Babel-related reasons) it should not affect anything

I'm not making an :advanced build.

We have :advanced builds, for production, but :preloads applies specifically to dev builds.

are you doing a RN production or dev build?

I see… so what does preloads do for you under dev?

Everything I'm doing with :preloads is with a dev build. It does nothing; the preloaded namespaces are never executed.

As I mentioned in my example above, I put a log to the JS console and it doesn't show up anywhere in logcat or the dev tools console.

I have gotten my logs to show up in my Cursive/IntelliJ REPL

via figwheel

You're missing my point.

and I can REPL into the device also…

sorry 🙂 please explain

My app works fine, in both debug and production. My logs work fine. I'm not talking about Babel or production builds. I'm just talking about :preloads and CLJS and RN, as the combination itself doesn't appear to work.

I apologize for any confusion.

got it… ok… I haven’t used those so I can’t comment then 🙂 wonder how :preloads really works, like how does it tell the browser/environment/etc to “preload” them

It tells the Closure compiler to execute those namespaces before loading cljs.core.

That's it, I think.

oh ok… before clojurescript core or before your own “main” fn?

like if it’s before ClojureScript core… how is anything working? 🙂

Before ClojureScript's core, and long before main.

oh wow… so like just … javascript?

Well, CLJS compiled to JS, yeah. So (.log js/console "meow") will be there, since you're in JS.

But you won't have println or map or anything.

probably my understanding of how Google Closure/ClojureScript works is limited in this scenario 🙂

ah I see.. so ClojureScript works

Yeah, just not cljs.core.

but no clojurescript core functions!

haha that’s funky

I like it haha

wonder if the output of :preloads is a separate file?

if that’s not sent to the device somehow, then it won’t work, since that’s the work of packager etc… but it should not be a fundamental RN limitation it sounds… I would look into how re-natal constructs the dev build file structure

Yep, I suspect it's something along those lines.