This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-24
Channels
- # announcements (5)
- # aws (24)
- # babashka (41)
- # beginners (130)
- # bristol-clojurians (2)
- # calva (39)
- # chlorine-clover (64)
- # cider (30)
- # clojure (202)
- # clojure-belgium (1)
- # clojure-dev (99)
- # clojure-europe (5)
- # clojure-hungary (4)
- # clojure-italy (10)
- # clojure-losangeles (8)
- # clojure-nl (11)
- # clojure-norway (6)
- # clojure-spec (7)
- # clojure-uk (12)
- # clojurescript (52)
- # core-typed (26)
- # cursive (19)
- # data-science (19)
- # datomic (19)
- # duct (10)
- # emacs (17)
- # fulcro (22)
- # graalvm (11)
- # jobs (3)
- # kaocha (28)
- # leiningen (6)
- # lumo (2)
- # malli (10)
- # nrepl (2)
- # off-topic (23)
- # pathom (2)
- # pedestal (7)
- # re-frame (3)
- # reagent (30)
- # reitit (2)
- # remote-jobs (2)
- # shadow-cljs (77)
- # sql (10)
- # test-check (22)
- # tools-deps (37)
- # vscode (1)
- # yada (3)
it looks like Enlive https://github.com/cgrand/enlive is abandonware (the "it hasn't needed attention and just works argument" notwithstanding [but correct me if I am wrong]).... last google group activity more than four years ago and last update other than the README half a decade ago...
are there other more current tools/approaches for getting data from the web commonly in use?
@patrickanium probably a better question for #clojurescript
Anyone used github actions to build a shadowcljs project? I would like to use https://github.com/peaceiris/actions-gh-pages to automatically build my shadowcljs project and publish it to gh-pages. Would be nice if I could use an existing action but couldn't find anything on the marketplace.
I haven't looked into github actions at all yet. I suspect it is pretty straightforward though
@thheller just wanted to say thanks for shadow-cljs! been a while since I used CLJS, and with shadow-cljs it seems that things gotten better
when using :browser
-target, and running shadow-cljs release app
, what is the HTML-file supposed to call in order to call the init
-function?
but when opening it after having released, my-ns
isn't available as a global variable
config file makes sense ๐ I looked here and couldn't figure it out: https://github.com/shadow-cljs/quickstart-browser/blob/master/shadow-cljs.edn
{:deps true
;; set an nrepl port for connection to a REPL.
:nrepl {:port 8777}
:builds {
:test {:target :node-test
:modules {:base {:init-fn token-streamer.main/init}}
:output-to "out/node-tests.js"
:ns-regexp ".*-test"
:autorun true}
}}
[:test] Compiling ...
========= Running Tests =======================
Ran 0 tests containing 0 assertions.
0 failures, 0 errors.
===============================================
[:test] Build completed. (46 files, 1 compiled, 0 warnings, 1.52s)
maybe my google fu is failing me, has anything been said before about bringing figwheel's "extra mains" feature to shadow-cljs?
as in any indication about how doable/hard/easy easy it would be, or if there's an alternative, or if there is a desire to have it or otoh a choice not to do it.
@lambder where are you tests? :modules
does not apply to the :node-test
target so if you expect that to do something it won't
@thheller they are a lot more lightweight than separate builds, that's really their main draw
you emulate extra-mains via modules if you really want to but I really don't quite see the point
might still be preferrable over having a handful of builds kick off in parallel. Thanks for the input.
ie. make 2 and one calls <script>my.app.init()</script>
while the other calls the tests
@thheller thanks. I managed to get the github actions for auto deploy to gh-pages to work. https://github.com/dakra/mui-templates
but now I see that it works nice locally with e.g. shadow-cljs watch app
but
when I make a release shadow-cljs release app
it doesn't show my chart
and some things doesn't seem to work without any error output.
I'm new to clojurescript, any tips to debug this or some common gotchas
I've to look out for that makes the release different from the dev version?
shadow-cljs release app --pseudo-names
or shadow-cljs release app --debug
will make things a little more understandable
Hmm. I don't see any difference with either --pseudo-names
or --debug
. I don't get 404 anywhere. it works almost as expected just recharts
is not displayed and some css looks slightly wrong which is correct when I do the dev build.
It's rendered here https://dakra.github.io/mui-templates/ and locally in dev mode it looks nice. (repo is https://github.com/dakra/mui-templates)
https://github.com/dakra/mui-templates/blob/master/src/mui_templates/dashboard.cljs#L94
That was a bit difficult for me as a clojurescript beginner to debug as there was simply no error anywhere