This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-03
Channels
- # adventofcode (1)
- # beginners (76)
- # boot (88)
- # cider (63)
- # clojure (357)
- # clojure-austin (2)
- # clojure-berlin (8)
- # clojure-brasil (8)
- # clojure-nl (1)
- # clojure-russia (22)
- # clojure-spec (17)
- # clojure-uk (47)
- # clojurescript (67)
- # cursive (45)
- # datascript (3)
- # datomic (45)
- # dirac (7)
- # emacs (3)
- # funcool (2)
- # hoplon (26)
- # jobs (2)
- # jobs-discuss (11)
- # luminus (6)
- # off-topic (243)
- # om (40)
- # om-next (7)
- # onyx (23)
- # overtone (1)
- # portland-or (2)
- # protorepl (11)
- # re-frame (55)
- # reagent (58)
- # rum (12)
- # sql (4)
- # test-check (12)
- # untangled (25)
for some reason boot-reload-hud font gone so small I canβt read anything on it. Anyone seen anything like it?
meh, nevermind.. apparently some smartass in sass-lib that Iβm using made {body { font-size: 4px}}
I'm trying to run my project but i ran into this problem http://dpaste.com/32FPRE2
when i run boot i get this message Classpath conflict: org.clojure/clojure version 1.9.0-alpha14 already loaded, NOT loading version 1.3.0
@lxsameer your libraries are bringing in incompatible versions of clojure
@lxsameer you can do boot show -p
to see which ones... then you can make a decision about which to bring in by making clj a direct dependency of your project
@juhoteperi with relax and calm and no rush, I rebased on master
, maybe we can deploy a 0.5.0-figwheel-SNAPSHOT
for folks to try out π ?
(plus of course merge the innocuous patch in boot-cljs
)
Okay, just one more test and boot-reload should be ready for release
aaand error π
@alandipert thanks man
@richiardiandrea asset-host is probably not too important for figwheel version
we can reimplement it later if needed
@juhoteperi Yep I am putting it as note for the future
if figwheel doesn't need it, probably we don't need it either
Should we just call figwheelified boot-reload boot-figwheel?
I think we need it because we use serve
which can be configured randomly...(maybe?)
@juhoteperi there is a boot-figwheel
project already
well, we'd use different group-id
or we could just keep using boot-reload artifact but change group-id and major version
congrats on the new boot-reload release!
@juhoteperi yes I just was thinking that it can be confusing a bit for folks to have two projects with the same name, but yes, and we have the powerlaces
group already
@richiardiandrea Ah, I was wondering what would be good group-id as boot
is reserved for core packages
yes we have powerlaces
for boot-cljs-devtools
already
I was also thinking about boot-clj, which would be the same as github org
Maybe @micha or @alandipert can also suggest what to use, I remember that powerlaces
was accepted when I proposed it as separate group (and Alan gave me permissions on Clojars). For me it is of course ok both ways.
@richiardiandrea Hmhm, I wonder why that if
is even necessary
probably related to warnings in cljs.core
yeah, I haven't investigated why to be honest
I trust Bruce on this π
@richiardiandrea don't follow what you are suggesting, can you bring me up to speed?
@alandipert I was wondering about new group-id for next boot-reload/boot-figwheel
I'm thinking about releasing the figwheelified version with another name and while at it, new github repo and use different group-id
I was suggesting powerlaces
group id like boot-cljs-devtools
but I am open to anything
oh, yeah
it's kind of weird for the owners to not be adzerk ppl
i think i like the idea more of making a new repo at a different org? for the figwheel direction stuff
At some point I'll probably also move boot-cljs to boot-clj github org
Perhaps I should do that now? We can still release under the old group-id
sounds good to me
for boot-reload, perhaps we keep the old one at adzerk-oss? we use it at adzerk and i can maintain it
so can I drop powerlaces
, or we keep it for non-boot-clj tasks?
I mean not core
well we still need some group-id for "core tasks"
boot
is currently only for Boot core and I think it is best to keep it as such, for security etc.
so powerlaces
! π
Would be good place to move boot-cljs to another group-id now that I'm planning on releasing 2.0.0
I am ok with that, I think you might need to ask @alandipert to be added to the clojars powerlaces
people
hmhm, I still do like boot-clj
better as it would be the same as github org
oh no, the namespaces are also named adzerk.
I changed a lot of stuff while porting
it was jupl.namespace
it's a breaking change
Hmm, now we get the notifications twice
mmm yeah
Might be fixed now
If we use powerlaces group-id, we could also have powerlaces github org
well, the two could be separate...
I like that we have everything in boot-clj
org
I guess it is fine
Naming stuff is hard
ah ah yeah
@juhoteperi do you want me to remote the group id from the new boot-reload
?
@richiardiandrea Figwheel branch? No need yet
yep ok
We should first decide what will be the name of new task
boot-figwheel or boot-figreload or something
oh I like the second
Maybe we can ask @ajchemist if he would be super super angry π if we name the task with the same name π
perhasp figreload would be good
yeah you know I like it too, it is as the name says, a mix between the too
so let's go for that
great
just lemme know the steps you want me to do
@richiardiandrea I created repo and pushed current boot-reload there
you could open PR there with the same branch as it old repo
but don't rename stuff for now, to keep the difference smaller
I'll rename everything once I have had time to go through the PR
gotcha I am doing it now
Enough coding for today, but I'll try to take look at PR as soon as possible so we can get first snapshot deployed
@juhoteperi thanks great
figreload
Is there anything special I need to do to eval code with cider if I'm using boot-cljs-repl? I'm connecting and running the repl, but when I try to eval a form, cider says cider-load-buffer needs a cljs repl.