On Monday, October 26, 2015 at 3:10:57 PM UTC+1, David Nolen wrote: > Based on what you've said so far it's not clear whether you misunderstand the > purpose of :modules. :modules is only about code splitting advanced builds. > It has nothing do with dependencies. > > > David
splitting compiled code and dependency management go hand-in-hand, don't they? (how would you load the code-split build without e.g. cljs.* present?) But that aside, is it intentional that if I do (ns mine.core (:require [mine.something :as something])) and (ns mine.something) and define a module to include mine.something and compile that module to a file something.js that this file something.js is essentially empty? -- 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.
