This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-08
Channels
- # beginners (92)
- # boot (2)
- # cljsrn (6)
- # clojure (33)
- # clojure-austin (1)
- # clojure-dev (18)
- # clojure-spec (7)
- # clojure-uk (2)
- # clojurescript (35)
- # cursive (13)
- # data-science (3)
- # datomic (1)
- # defnpodcast (1)
- # figwheel (1)
- # fulcro (27)
- # instaparse (1)
- # java (2)
- # leiningen (8)
- # off-topic (5)
- # onyx (1)
- # portkey (2)
- # re-frame (9)
- # reagent (2)
- # ring-swagger (1)
- # shadow-cljs (136)
- # test-check (3)
- # tools-deps (29)
Just spotted a spurious dependency on [refactor-nrepl "2.3.0-SNAPSHOT"]
in my lein deps :tree of my current project. This came in via my clojar library image-lib
. Turns out it was getting included by lein deploy clojars
from the dev
profile of image-lib. It no longer needs to be there, so its an easy solution just to remove it and re-run the deploy. BUT I'm puzzled as to how it got in there. Doing a lein deploy shouldn't be looking in the dev profile should it?
agreed
I've never seen that happen
I also have [expectations "2.0.9"]
in the dev dependancies and that doesn't get included. Probably not worth worrying about but I will be keeping a closer eye on my dependency trees in future.
is it possible one of your real deps has a dependency on it?
There are only 2:
:dependencies [[org.clojure/clojure "1.7.0"]
[com.novemberain/monger "3.0.1"]]
And removing refactor-nrepl from the dev dependancies and redeploying got rid of it.welp I guess computers just don't work
I have a project with 2 config files, depending on the environment: <project>/env/dev
and <project>/env/prod
.
project.clj
configures different source-paths
for different :cljsbuild
s. In the different builds, there's one that uses :figwheel {:on-jsload ...}
On running lein figwheel
, the compiler uses the right config (dev). On hot module reload, the wrong config file is used (prod).
Why does hot module reload takes another config file (another source-path
)?