This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-30
Channels
- # announcements (4)
- # babashka (3)
- # beginners (5)
- # calva (20)
- # cider (12)
- # clj-kondo (7)
- # cljs-dev (2)
- # clojure (76)
- # clojure-uk (4)
- # clojuredesign-podcast (8)
- # clojurescript (18)
- # clojutre (1)
- # cursive (9)
- # data-science (27)
- # datomic (2)
- # fulcro (32)
- # graalvm (4)
- # jackdaw (5)
- # jobs (2)
- # joker (5)
- # lumo (20)
- # off-topic (18)
- # pathom (3)
- # shadow-cljs (18)
- # sql (5)
- # tools-deps (1)
- # vim (11)
I have builds targeting :browser-test
and :karma
. Is there some easy way to exclude some (heavy) tests from the browser test suite only? Ideally on a test-by-test basis, not ns.
Unrelated, but I use to have to monkey-patch nextTick: (gobj/set shadow-js/process "nextTick" goog.async.nextTick)
. Updated shadow-cljs from 2.8.36 to 76 and shadow-js/process
is now undefined, however I remove the monkey patch and the tests pass. Did that implementation change or are my tests broken?
vim-salve says it supports Leiningen, Boot, and the Clojure CLI. Does that mean that if I use deps.edn with shadow-cljs, vim-salve will support it too? I'm presuming that to be the case based on this bit from the docs: > The new deps.edn can also be used to manage your :dependencies and :source-paths instead of using the built-in methods or lein. All shadow-cljs commands will then be launched via the new clojure utility instead. https://shadow-cljs.github.io/docs/UsersGuide.html#deps-edn
if its just about starting a clojure jvm then yes deps.edn will work and you can use shadow-cljs via that
vim-salve is supposed to be helpful for setting classpath in vim, so that tools like vim-fireplace can better interact with the REPL to do things like reading docstrings and navigating to source.
I'm fairly new to Clojure and trying to get my editor running smoothly, but still getting a few errors here and there.
One thing I notice is that npx shadow-cljs classpath
does not list the source path entries that shadow-cljs info
produces. Is that normal? My understanding is that the classpath should be a combination of the given filesystem directory and .jar file entries, so if I have :source-paths ["src/main" "src/test"]
, I expect them both to be in the classpath.