This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-10
Channels
- # announcements (4)
- # beginners (111)
- # calva (12)
- # cider (10)
- # cljdoc (1)
- # cljs-dev (7)
- # cljsrn (4)
- # clojure (38)
- # clojure-houston (1)
- # clojure-serbia (3)
- # clojure-spec (22)
- # clojure-uk (26)
- # clojurescript (4)
- # cursive (1)
- # data-science (1)
- # datomic (12)
- # klipse (1)
- # off-topic (25)
- # pathom (9)
- # protorepl (3)
- # quil (4)
- # shadow-cljs (43)
- # tools-deps (24)
@deadghost yes if you directly :require
the namespaces will be moved to that module and cannot be code-split
lazy-component
however is just a proof of concept that combines it with React components
you could just as well load an entire map for example if you want to group something
@thheller killer, thank you. would I just bind to the install/activate/fetch events? there's no higher level abstraction there yeah?
I generally recommend using a better suited tool like https://developers.google.com/web/tools/workbox/
but I've only experimented with super basic service workers so CLJS might get better the more you do (if you do)
yeah I'd eventually at least like to develop my own toolkit, fortunately I'm not in a position where I need to be systemic about it
I want write a macro which used to define style in cljs. when the macro expand, generating css file to somewhere
if some cljs using this macro is already compiled, it will be cached and won't compile again?
but does it matter if this macro will be used only in application code, not used as a dependency for library
I want to generate css, with following features
1. always keep the class
property sync with the selector
in css.
2. less runtime stuff, as static as possible
3. manipulate style with functions