Stupid question: So, with the new Node package interop, do I add the NPM deps to the Project.clj or just the Build.clj?

Has anyone seen this warning before? WARNING: Use of undeclared Var cljs.js/lib at line 450 …/.boot/cache/tmp/…/app/cm9/pref5e/public/js/app.out/cljs/js.cljs

@borkdude Yes. It is fairly innocuous and an (if anything) affects self-host: https://dev.clojure.org/jira/browse/CLJS-2141

Why is the AST for ((fn [a b] (+ a b)) 5 7) almost 3000 lines long? For proof, see http://tiny.cc/cljs-ast

Real question, that site’s just a place to see for yourself

it's got the environment expanded at every node... most of the bulk is under :env keys

because AST is very verbose

looks like there's a lot of :js-globals that are repeated in various nodes

most of those are actually the same identical object referred to from multiple locations

huh

is there a way to get a brief version?

Like an existing AST-cleaner lib

https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/analyzer/utils.clj#L12-L22

oh, sweet. I’ll check that out.

@bronsa I can’t seem to require that namespace in figwheel. (require '[cljs.analyzer]) works but (require '[cljs.analyzer.utils]) doesn’t.

@chalcidfly That code is Clojure (it is in a file ending with *.clj; you’ll need to essentially copy the relevant code you desire to a ClojureScript file (`*.cljs` or *.cljc)

oh, thank you.

Is there a tool that people here use to detect things like unused namespaces in .cljs files?

@rgdelato Thanks, I’ll take a look!

@rgdelato find ./src -type f -name "*.cljs" | xargs -n 1 joker --lintcljs worked quite nicely!

how would you make a function like keyword that takes a string and makes it a fully qualified keyword in the current namespace?

user=> (keyword "foo-bar.spam" "meow")
:foo-bar.spam/meow

I found that apparently you can't get the namespace at runtime in cljs, so I got the namespace in a macro via (get-in &env [:ns :name]) instead

if i'm writing code to manage state in a SPA / re-frame app that has to interface with a remote API, does it make sense to use core.async? or should i just go with something simpler like a promise library?

@yedi just use promise/deferred if all you have is request/response cycle

core.async would make more sense if you would have complex data flow in the app, like many dependent requests for example

sounds good, thanks

FWIW I think core.async is much simpler to use than promises

also a bigger dependency to take on