This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-22
Channels
- # beginners (104)
- # bitcoin (1)
- # boot (5)
- # clara (3)
- # cljs-dev (14)
- # cljsjs (5)
- # cljsrn (1)
- # clojure (242)
- # clojure-italy (17)
- # clojure-news (13)
- # clojure-norway (3)
- # clojure-russia (101)
- # clojure-spec (41)
- # clojure-uk (87)
- # clojurescript (38)
- # core-async (38)
- # cursive (6)
- # datomic (11)
- # defnpodcast (3)
- # docs (14)
- # editors (8)
- # events (1)
- # fulcro (7)
- # hoplon (25)
- # leiningen (4)
- # luminus (7)
- # off-topic (25)
- # onyx (1)
- # portkey (14)
- # random (1)
- # re-frame (7)
- # reagent (4)
- # rum (4)
- # schema (8)
- # shadow-cljs (257)
- # spacemacs (10)
- # specter (4)
- # unrepl (3)
- # yada (1)
or just a :post-process-hooks [processor1 processor2]
where each "processor" is a function takes the compile configuration and has the compile-env already bound.
@bhauman you are basically describing the idea behind shadow-cljs
… thats why it has :target
:browser
, :node-library
, :node-script
, :npm-module
and can easily be extended to more
:target
basically defines how the final code is bundled together and takes different configuration accordingly
the example is a bit old but it is create-react-native-app
out of the box with no modifications working with specially bundled CLJS code
@bhauman not particularly interested in a public thing - if there’s some internal hook you’d like to see, then we can talk about that
@alexmiller so the only enhancement here is to look for the cljc as well right ?
I mean in Clojure
I have no idea in CLJS