Assume I got modules compilation with cljsbuild to work (with a local 1.7.160
build, because .145 is broken in that regard, put the 1.7.160-aot.jar into my
lib/ and be happy it works).
Assume I have ns "mine.something" and "mine.core" and a :modules entry
{:something {:output-to ".../something.js" :entries #{"mine.something"}}}
#1 If I do not require mine.something in mine.core (or elsewhere,
transitively), and compile the sources, I get a something.js with content as
one would expect, representing the code defined in something.cljs, but does not
include the dependencies - neither view google dependency calls nor via code
inclusion.
Is there a way to control dep inclusion? (as in:
- don't include any deps,
- include those deps that are specific to myself but not those present already,
- include all my deps, including cljs itself)
Without this capability modules need management of their dependencies basically
in a manual matter, which is .. suboptimal.
#2 If I require mine.something in mine.core, and compile the sources, I get a
something.js with no content other than the source map file comments, like
//# sourceMappingURL=something.js.map
Instead its code is compiled into the same output as the using namespace is
being compiled to (here: mine.core, i.e. to cljs-base.js)
I believe this is a bug.
Regards,
-Martin
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.
