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)
There is docs about how to add a single cljs
file on a (possibly) complex react/jsx/npm
project?
@thheller: I think I may have figured out the problem I had yesterday (lot's of provide conflicts). I happened to notice that the .jar
of one of our dependencies (https://github.com/vimsical/re-frame-utils) from clojars contains a directory called out
(6.2 megabytes), which in turn contains cljs
, goog
, .. re_frame
, .. reagent
.. and a bunch of other compiled js libraries. Now I'm no expert on building packages, but that doesn't seem quite right?
@lasse.maatta yes. that is not correct and should not be done
Hi, I’m moving from leiningen and figweel to shadow-cljs.
I’m doing a single re-frame app that has a db.cljs file with the specs and a handler.cljs file with the database initialization. after the initialization there is an interceptor used for debug
(def check-spec-interceptor
(after (partial check-and-throw :custodian_assets.db/db)))
but I’m getting this error
alpha.cljs:71 Uncaught Error: Unable to resolve spec: :custodian_assets.db/db
at Object.cljs$spec$alpha$reg_resolve_BANG_ [as reg_resolve_BANG_] (alpha.cljs:71)
at Object.cljs$spec$alpha$Specize$specize_STAR_$arity$1 (alpha.cljs:128)
at Function.cljs$core$IFn$_invoke$arity$1 (alpha.cljs:124)
at Function.cljs$core$IFn$_invoke$arity$1 (alpha.cljs:141)
at Function.cljs$core$IFn$_invoke$arity$2 (alpha.cljs:359)
at custodian_assets$handlers$check_and_throw (handlers.cljs:14)
at Function.G__14213__2 [as cljs$core$IFn$_invoke$arity$2] (core.cljs:4268)
at re_frame$std_interceptors$after_$_after_after (std_interceptors.cljc:313)
at Object.re_frame$interceptor$invoke_interceptor_fn [as invoke_interceptor_fn] (interceptor.cljc:68)
at Object.re_frame$interceptor$invoke_interceptors [as invoke_interceptors] (interceptor.cljc:106)
What am I missing?
Hi, quick question - I’m trying to use https://github.com/gadfly361/soda-ash/blob/master/src/soda_ash/core.cljs , which has (:require [cljsjs.semantic-ui-react]…
in it. This adds about 600 files to my dev build, but when it’s compiled for production, only the actually used components will remain, or b/c it’s cljsjs
, it’ll keep the whole semantic ui code? Thanks!
so cljsjs stuff (i think i heard you say this in a podcast?) is best to avoid when using shadow?
you can only requite whatever you need manually but when including the root package everything will be included
does it make sense to try to control two different browser apps from a single shadow-cljs.edn
file?
and/or does it make sense/is it possible to change source paths per app? or does the namespacing make that irrelevant? (sorry, my first cljs app…)
@hoopes :source-paths
can only be configured once per shadow-cljs.edn
, not per build. you run have multiple builds per config though that is perfectly fine. only code used in a build will actually be compiled
Hi all. I have confusing issue regarding paths. How to solve situation where application in prod sits on some path like http://mydomain.com/coolapp but in dev there is no need for /coolapp path? in index.html I have /coolapp but then having issues with paths in dev.