This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-29
Channels
- # 100-days-of-code (2)
- # bangalore-clj (1)
- # beginners (141)
- # cider (33)
- # cljs-dev (13)
- # cljsjs (7)
- # cljsrn (1)
- # clojure (88)
- # clojure-conj (3)
- # clojure-dev (24)
- # clojure-italy (11)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-sanfrancisco (1)
- # clojure-spec (4)
- # clojure-uk (53)
- # clojurescript (65)
- # core-logic (2)
- # cursive (28)
- # datomic (33)
- # duct (2)
- # emacs (3)
- # figwheel-main (9)
- # fulcro (44)
- # hoplon (6)
- # leiningen (144)
- # mount (1)
- # nrepl (21)
- # off-topic (102)
- # onyx (2)
- # other-languages (5)
- # pathom (6)
- # planck (3)
- # portkey (1)
- # re-frame (7)
- # reagent (5)
- # reitit (17)
- # shadow-cljs (24)
- # spacemacs (16)
- # tools-deps (64)
- # uncomplicate (2)
- # vim (22)
Has anyone tried deploying ClojureScript to http://cloudflareworkers.com ?
Hello, regarding reagent
; is it a good idea to pass into a component a callback that updates a ratom?
@polkafreaku You’ve probably hit the point at which re-frame starts becoming relevant.
A rule of thumb I use for myself is that when I start wanting to wrap updates and reads to/from ratoms in functions, the project has grown enough for re-frame to be a better choice than plain Reagent.
Yeah, I’ve tried delaying it, and I just end up with poorly implemented version of a quarter of re-frame ^_^
Self-hosted ClojureScript error when trying to eval (+ 1 2 3)
: WARNING: Use of undeclared Var cljs.user/+ at line 1
. What am I doing wrong? Is this loader related? Caused by shadow-cljs?
I have two builds in my shadow.cljs.edn, one with :target :browser, and another with :target :bootstrap. I run shadow-cljs watch app bootstrap. Is that what you mean by bootstrap bundle?
here's an example of bootstrapping your environment: https://github.com/Lokeh/lilac.town/blob/master/src/lilactown/client/visual_spec.cljs#L170
I also found that using cljs.env/default-compiler-env
as vs-env
was useful, can't remember why
thx, I wasn't calling boot/init
. Will this work in release, though? Feels odd to pass in js/bootstrap
as path.
What is the "bootstrapped bundle"? Is it like a standalone build with a set of namespaces?
https://code.thheller.com/blog/shadow-cljs/2017/10/14/bootstrap-support.html explains it
I have two builds in my shadow.cljs.edn, one with :target :browser, and another with :target :bootstrap. I run shadow-cljs watch app bootstrap. Is that what you mean by bootstrap bundle?
here's an example of bootstrapping your environment: https://github.com/Lokeh/lilac.town/blob/master/src/lilactown/client/visual_spec.cljs#L170
I also found that using cljs.env/default-compiler-env
as vs-env
was useful, can't remember why
thx, I wasn't calling boot/init
. Will this work in release, though? Feels odd to pass in js/bootstrap
as path.
Hi, I have a small ClojureScript library that I have been developing with the Clojure CLI tooling. I'm now at the stage where I want to publish my library so that I can use it in another of my apps (which is built with boot). I think I'm correct in my assumption that the easiest path is for me to generate a JAR (not an uberjar) and publish to Clojars. It doesn't look like the Clojure CLI provides any tools out of the box for building a JAR. What's the easiest way to package up my library into a JAR that is ready for Clojars publishing (ideally without the need for requiring Boot or Leiningen)?
Thanks @U1UQEM078, depstar looks like it could be a good option. I notice you pointed me to the seancorfield/depstar
fork of healthfinch/depstar
. Is there specific functionality only available in the fork?
IIRC, it's usually required for making runnable jars and wars. I'm not sure what clojars expects there 😕
Ok, well my library is designed to be utilised by other ClojureScript apps, as opposed to being runnable itself
https://github.com/juxt/pack.alpha/blob/master/README.adoc#uploading-to-clojars-or-maven
Thanks @U09LZR36F, looks like Pack is a good option
the dereferencing of infix-expression
has to happen inside of a component when it's rendered
Hello... I'm trying to get off the ground with a cljs repl connected to the browser. The caveat is that my server is running on a separate host. This means two things: (1) cljs.main --repl
can't launch the browser, but that's fine because I can connect directly to my host gargan.jupiter:9000
; (2) I need the browser to supply the repl using the same host and port, but it keeps trying to connect to localhost:9000