@mhuebert if you just want to know the macro namespaces the data should already be available, getting the dependencies of macro namespaces however is much trickier

since clojure is much more dynamic than CLJS

@thheller is that because of dynamic statements outside of (ns..) forms that wouldn’t be captured by traversing with a parse-ns-style function?

yes

load-file as well, or rather load

tools.namespace has some things but they only work reliably when you actually load all namespaces

ns in CLJS is never eval’d and only static information

in CLJ it is actually a macro

but you can get far enough with just parsing the ns

it just won’t be complete

I see.

but should be good enough since macro namespaces intended for CLJS don’t get very complex usually

and don’t pull in too much CLJ code

I can recommend using the clojure.core.specs.alpha specs to parse the ns form

but tools.namespace really should have everything you need

So I suppose when bundling for self-host, we’ll only need to worry about precompiling macros that work in cljs. We can use other (precompiled) dependencies that use Clojure-specific macros, but those macros don’t come along for the ride

I have never actually used self-host, I don’t even know how the macros work there 😛

🙂

there is some weirdness subtlety

so if limiting to self-host-compatible macro files, then using cljs.analyzer to get the ast of the ns form should be ok (found that via analyzer.api/parse-ns)

CLJ ns is a bit different and some things won’t be supported

oh parse-ns might not work since it assumes to read from the file right?

hmm yeah, it will read the file with :read-cond :cljs

I’m not using parse-ns directly but pulled out the important parts

is there an example repo that does :advanced compilation of react? (with all the required workarounds)

@thheller here https://github.com/roman01la/scrum-ssr-example/tree/react (not plain React, but with a wrapper library, Rum)

hehe thx, I found that like 5min ago

I remembered you did something like that

why do you include ALL externs? it seems that only the plugins are required?

or is there anything else I might be missing? only testing on a very basic example currently

I don't know if it's because Rum or Sablono is using some interop unsafely, but in case of this app it's not only event plugins

Too lazy to find out :)

wasn’t CLJS 6 yesterday?

https://www.youtube.com/watch?v=tVooR-dF_Ag&t=1s

this says 7/20/2011

the boostrap powershell script (and some others) is out of date, should I open a jira ticket for that, or pr?

@moxaj I’d recommend opening a JIRA, and if you’ve signed the CA, submit a patch that fixes them

Also, @moxaj you could add an analog of script/clean if you have one