This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-27
Channels
- # announcements (2)
- # babashka (60)
- # beginners (73)
- # calva (23)
- # cider (2)
- # clj-kondo (19)
- # cljs-dev (31)
- # clojure (29)
- # clojure-berlin (1)
- # clojure-europe (6)
- # clojure-nl (17)
- # clojure-spec (21)
- # clojure-uk (15)
- # clojurescript (54)
- # core-async (48)
- # cursive (35)
- # datomic (12)
- # emacs (12)
- # fulcro (66)
- # graalvm (3)
- # graphql (16)
- # jackdaw (1)
- # malli (1)
- # off-topic (11)
- # pedestal (4)
- # re-frame (10)
- # reitit (1)
- # rewrite-clj (8)
- # ring-swagger (8)
- # shadow-cljs (14)
- # spacemacs (2)
- # vim (5)
can I use some css file installed by npm install
without copy them into resources/public
? should I use webpack? or there is a some simpler way?
@U052XLL3A great idea!
Using shadow-cljs and deps.edn
together - what is the minimal amount of configuration necessary?
Reading https://shadow-cljs.github.io/docs/UsersGuide.html#deps-edn, it's suggested to use :deps true
in the shadow-cljs.edn
config file, but below that, it's stated that one must add thheller/shadow-cljs
to deps.edn
, and the example states to add it in :extra-deps
, which in turn seems to require an alias, according to both the example and the deps ref: https://clojure.org/guides/deps_and_cli#extra_deps.
Using an alias in turn means that :deps true
is not enough, since one need to specify the alias, eg :deps {:aliases [:cljs]}
.
If this is correctly interpreted, I'd suggest removing the :deps true
example for the next newcomer 🙂
Sure, but if it's not possible at all to use :deps true
, it might be a blocker, especially for newcomers.
Moving some dependencies under aliases just makes sure that you don't bring unneeded stuff along. Well, most of the time. Since you don't need shadow-cljs to actually run release versions of applications, it makes sense to move it under an alias that's only used during the development and UI release.
I’m running tests for my browser application using the node-target
, but now I have some code that uses js/window
and am trying to use jsdom
in a sensible way. The best I’ve come up with so far is conditional initialization in src
files, i.e., if there is no window present, make a fake one with jsdom
. I’m curious if there’s a better way, though. Would build hooks be a possible alternative? Does anyone have any experience with this problem?
In create-cljs-app I just made a node only entry point that adds jsdom