I'm reading cljs.analyze/analyze-file, it states: "does not return a meaningful value"

did it return a meaningful value in the past?

@bensu: it may have returned IJavaScript, but I don’t remember anymore

would have to go through the git history

dnolen: ok thanks, I'll look at it then.

@dnolen: in any case, I should see it's side effects from env/*compiler* right?

@bensu: yes

when analyzing files with cljs.analyzer/analyze-file it is necessary to load them in dependency order right?

@bensu it depends

there flags for this stuff

analyze-deps is optional

but if you enable that, then it will visit the deps in order before proceed to analyze the current file to avoid warnings

ok, what about cljs.core and goog.{}?

will it analyze those as well in order to avoid warnings?

I'm asking because it seems to be analyzing cljs.core and then throws an Exception because it can't find goog.string

solved. Using the analyzer from the REPL is very fun

@bensu analyzer can’t analyze JS yet it skips JS stuff

@bensu cljs.compiler has with-core helper to analyze cljs.core first so the compiler state is populated

@dnolen: thanks, it makes sense, I'll read the helpers then.