Not sure I understand what you mean. What do you mean by "main module"?
cljs has a notion of a base module, while shadow-build does not.
Typically your ns structure and the requires are enough to establish
relationships between them so shadow-build can figure out what needs to be
where. If that
Thomas,
I as well think modules is the right approach when using web workers.
What can I do if my app code is build from many namespaces? How do I tell
the main module to use all of them? Do I have to list them ALL?
On Friday, February 19, 2016 at 5:54:59 PM UTC+2, William la Forge wrote:
>
> C
Hey,
I have seen Servant but I do not like it. In general I do not like
solutions that use macros to solve problems a build tool should solve. YMMV.
cljs-runtime is the directory used by shadow-build for all compiled files.
The structure it creates is that you have one directory, with a .js fil
Thomas,
Your worker demo includes the entire cljs runtime as part of the
project?
https://github.com/thheller/worker-example/tree/master/demo/js/cljs-runtime
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to cloju
Thomas,
Have you seen this? A simple demo using workers in
clojurescript: https://github.com/MarcoPolo/Servant
I've converted the demo to use
boot: https://github.com/aatree/aademos/tree/master/servant-demo
--
You received this message because you are subscribed to the Google
Groups "Clojure"
Thomas,
Modules looks quite exciting. I would be glad to help in developing a boot
task for same.
Bill
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members a
Hello,
I'm not quite sure what you are saying here since I do not know boot or
hoplon or durable-cells.
I can however suggest a "better" solution for Workers: Using Closure
Modules.
CLJS or boot do not implement them for :none at the moment but shadow-build
does. I also have a few extra hints
Compiling with optimizations none is no doubt quite handy, especially in
conjunction with source maps, as a traceback will take you to the line of
code causing the problems, and with the same variable names used in your
original clojurescript code. But this is not currently possible for .jc
f
