On Fri, Dec 19, 2014 at 11:29 AM, Arnaud Bailly <[email protected]> wrote: > Thanks for your answer. > > Actually, I am not using :none. As advocated on cljsbuild page and Om > tutorial, I have tried to use two configurations, one for dev with no > optimisation, one for prod with advanced optimisations. Problem is that > structure of JS within HTML pages is not the same so one has to change HTML > between the two settings, which is not very practicle. It seems that > boot-cljs handles that for you but did not tried it.
There's an open ticket to address this which needs much review & consideration. In the meantime this is entirely solvable in the same way it has been solved in many web frameworks (Rails, Django, etc.) - use environment variables to configure the generated markup. environ, https://github.com/weavejester/environ is good for this. > Moreover, I feel uncomfortable using different settings for prod and dev in > something as important as the produced javascript code. I would like to be > sure I find compiler issues (mine or others') in dev, not in production. Of > course, I have ETE tests to catch that kind of stuff but again, I tend to > think it is best to have dev and prod settings as close as possible. Or maybe > I am wrong? Your discomfort seems very misplaced to me. Deployed JS/CSS artifacts in most production websites are rarely ever the same as what was dev'ed with for good reason - you absolutely want concatenation & minification in production. David -- 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.
