This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (16)
- # aws (9)
- # babashka (76)
- # beginners (92)
- # boot (1)
- # cider (18)
- # clara (7)
- # clj-kondo (26)
- # clojure (104)
- # clojure-europe (4)
- # clojure-nl (11)
- # clojure-spec (11)
- # clojure-survey (101)
- # clojure-uk (35)
- # clojuredesign-podcast (15)
- # clojurescript (8)
- # core-async (29)
- # data-science (1)
- # datomic (13)
- # emacs (4)
- # fulcro (20)
- # graalvm (14)
- # instaparse (2)
- # jobs (1)
- # juxt (6)
- # malli (5)
- # off-topic (30)
- # onyx (3)
- # planck (1)
- # project-updates (7)
- # re-frame (38)
- # reagent (30)
- # reitit (14)
- # remote-jobs (2)
- # shadow-cljs (50)
- # sql (8)
* Q: Which ClojureScript tools do you use for interactive development? ** ClojureScript's built-in REPLs ** Figwheel Classic ** Figwheel Main ** lein-cljsbuild's command-line REPL ** shadow-cljs ** Dirac ** Devcards ** cljs-devtools ** Other [open response] * Q: How are you running your ClojureScript tests? ** Headless browser (or actual browser) ** Node.js ** Nashorn ** Devcards ** Phantom ** doo ** Karma ** shadow-cljs ** Kaocha ** nubank/workspaces ** Figwheel ** I don't have any tests! ** Other [no response]
the first is in replacement for the prior "CLJS REPL" question, both have updated answer sets. what's missing?
@alexmiller cljs-devtools is a library that is usually used during development with any other tool. doesn't seem to fit into the question?
I think you're suggesting you would not use cljs-devtools during interactive dev and it should be removed?
no you would absolutely use cljs-devtools but you can't just use cljs-devtools. you still need something to compile the code. it is just a library.
maybe a separate question like "what libraries do you use frequently?" or so makes sense
also the first answer should probably be
cljs.main (as that covers the REPLs and more)
first answer for which question? and do you mean replacing the existing one or inserting?
* Q: Which ClojureScript tools do you use for interactive development? ** ClojureScript's built-in REPLs
kind of ... you have it in both right now. if you want both than libraries in the same category (eg. workspaces) should also be in both
there is a lot of overlap after all. you could be using devcards with shadow-cljs or figwheel after all.
specifically for "deps definition and download" and one for "creating project artifacts"
yeah I would probably combine those 2 questions then. otherwise you just keep repeating tools that cover those aspects and more (eg. shadow-cljs or figwheel)
I’m curious (no idea if anyone else is or if it’s relevant) how many people are coding or would like to code more
cljc based code. I personally aim to do most of my development in that space and I think knowing whether it’s a niche area or not would be useful?
Not sure what’s currently in the survey, so no idea if it’s already addressed…
it's not currently mentioned anywhere. certainly not niche - many people doing this. I'll think about where and whether to add it.
It’s an area that still feels like it has a lot of sharp edges, I’m ok dealing with it if it’s not a priority, but otherwise would be good to know that I should be highlighting issues or picking things to work on =)…
I've tweaked the portability answer in the "What has been most frustrating or has prevented you from using ClojureScript more than you do now?" to include it explicitly
or combined variant:
* Q: Which ClojureScript tools do you use for interactive development and testing? ** cljs.main ** ClojureScript's built-in REPLs ** Headless browser (or actual browser) ** Node.js ** Nashorn ** Phantom ** Figwheel Classic ** Figwheel Main ** lein-cljsbuild's command-line REPL ** shadow-cljs ** doo ** Karma ** Kaocha ** Dirac ** Devcards ** nubank/workspaces ** cljs-devtools ** Other [open response]
> Q: Which ClojureScript tools/libraries do you use for interactive development and testing?
dunno if it makes sense to separate but in my view some of these don't qualify as "tools", rather something you use with those tools.
both of the original questions (about CLJS repls and CLJS testing) were specifically added to assess the status quo wrt how people were doing these things (and pre-dated things like Figwheel)
yeah there is lots of overlap in the answers so I guess its kinda difficult to have "generic" answers
but its good to list stuff that people may also be using separately with handmade tools
I'm looking at changing them because I no longer felt like the REPL question was actually reflecting how people work. yes, they use REPLs, but in the context of larger environments or in combination with other things (and maybe not even just on ekind of RPEL). Maybe similarly for testing where something like Devcards seems to be equally as useful, but very different in some ways than traditional "test runners".
so my meta question is: what questions are useful to ask to assess how people work with developing ClojureScript apps?
Part of this is also tooling I think, I didn’t realise the value of a clojure repl vs say a python interpreter until I could get inline send form to repl working, it’s still really not great in clojurescript in my experience… IE, people with different workflows will have wildly varying perspectives…
I would like the results of this question or questions to answer "how do people usually work with ClojureScript?"
assuming you already have a separate question regarding build tools it might make sense to not repeat them in that question
and instead focus on the feature they provide, eg. "Hot-Reload" provided by the build tool (figwheel or shadow-cljs)
hot-reload is a big part of my workflow ... I barely use the REPL for CLJS yet the REPL is my primary tool for CLJ
yeah that would be interesting too. I would be curious to see how many actually use the recommended webpack+cljs.main combination vs cljs.main+cljsjs
Ah, I was under the impression that was more of a, for those who wish to use it this way, rather than, this is how you should do it…
it you are just using react via CLJSJS that is fine. but if you use 20 different packages from npm you'd probably not use CLJSJS but rather shadow-cljs or webpack+cljs.main
so as additional options to "What tools do you use to define and download your dependencies?"
** npm (package.json) ** shadow-cljs and yarn ** webpack and cljs.main
sorry. JS deps are always managed by either npm or yarn (which both define the dependencies in package.json)
you typically use one of those and then consume the packages with either shadow-cljs OR cljs.main+webpack
I guess for the purposes of that question, probably only
npm or yarn (package.json)
I have another question "What tools do you use to create project artifacts for release/deployment?" and I will have both shadow-cljs and cljs.main in there
do you have shadow-cljs in the "define and download dependencies"? it can do that as well 🙂
:dependencies. same format as
:dependencies (same library in fact, pomegranate)
lots of people use shadow-cljs either standalone or with deps.edn/project.clj. would be interesting for me to see some numbers behind that 🙂
@alexmiller we use cypress as well for testing UI flows in the browser - i’m not sure if that’s helpful for this survey though
a few people mentioned that in last year's open responses but not enough that I had added it
condition systems and monadic failures are not idiomatic, but feasible and some people do those