This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-20
Channels
- # admin-announcements (1)
- # bangalore-clj (4)
- # beginners (176)
- # boot (38)
- # cider (9)
- # clara (1)
- # clojars (9)
- # clojure (290)
- # clojure-belgium (25)
- # clojure-berlin (2)
- # clojure-dusseldorf (10)
- # clojure-italy (1)
- # clojure-russia (141)
- # clojure-sg (1)
- # clojure-spec (40)
- # clojure-uk (38)
- # clojurebridge (19)
- # clojurescript (148)
- # code-reviews (37)
- # community-development (7)
- # cursive (27)
- # datomic (71)
- # editors-rus (3)
- # events (1)
- # heroku (1)
- # hoplon (16)
- # jobs (5)
- # lambdaisland (3)
- # lein-figwheel (211)
- # luminus (3)
- # off-topic (52)
- # om (18)
- # onyx (49)
- # overtone (3)
- # pedestal (48)
- # protorepl (7)
- # rdf (2)
- # re-frame (61)
- # reagent (3)
- # timbre (2)
- # untangled (69)
is it expected that the watch
task can result in a large number of WatcheService threads like this?
"WatchService for resources/public/compiled/js/goog/debug" #601 daemon prio=5 os_prio=31 tid=0x00007f7f762ec800 nid=0xc1703 runnable [0x00007000084bf000]
at com.barbarysoftware.watchservice.MacOSXListeningWatchService$CFRunLoopThread.run(MacOSXListeningWatchService.java:73)
...
"WatchService for src/styles" #531 daemon prio=5 os_prio=31 tid=0x00007f7f77096800 nid=0xb4b07 runnable [0x0000700003cea000]
at com.barbarysoftware.watchservice.MacOSXListeningWatchService$CFRunLoopThread.run(MacOSXListeningWatchService.java:73)
i currently have 239 "watcher threads" (according to jstack
) on a medium sized project. it jumps to ~300 if i turn on the cljs compilation step in my build.I think I'll release next boot-cljs as 2.0.0
. Not that it'll be different in any major way, but I think following compiler version is no longer needed, and I think there is no reason to wait for "the major update" I've been thinking about.
@juhoteperi have you had time to have a look at figwheel client in boot-reload
by any chance?
@richiardiandrea I have looked at it quickly. It is still missing some event types?
yes css and some other things...also there is a call to cljs.compiler/munge
that I would like to discuss with you, personally I don't like it
as it includes a dependency on clojurescript
it is there because figwheel requires the munged javascript namespace
Can boot-cljs get the munged name without using the same cljs.compiler/munge
call?
yes that's what I was thinking, but that would be some meta on the changed js file...that's the burden it adds
@micha yes I was thinking exactly that, now the only meta we pass around is on the .cljs.edn
Yeah, that is one option.
mmm...I am still torn between the two...because in any case boot-cljs
and boot-reload
are going to be used together...and in any case the project requires clojurescript
The dependency is not problem. Problem is that munge
is not in the public API.
ah yes, true, figwheel uses it deliberately...maybe it should be public...I have no idea why it is used, the end result is just do have _
instead of -
I guess
well, no: it does other stuff: https://crossclj.info/ns/org.clojure/clojurescript/1.9.293/cljs.compiler.html#_munge
Hi guys, I'm trying to build an open source project to make available on maven central repo through OSSRH
Do u guys have any nice tutorial available explaining how to make it? Tried to google a lot, but just found tutorial about clojars
Asking here because I'm using boot
@iago.b2wdigital are you running into issues pushing to maven central?
Well I do boot pom but I can't find the pom.xml anywhere
Cool, that helps.. it's required that all files must be signed
Does boot sign the files like maven?
Cool.. so to push the files I could do almost the same process as to publish to clojars, like in the tutorials?
you can also create the pom and jar with boot and then use mvn
to push them to maven central probably
Well, thanks a lot then.. it's the last step to make it open source :)
Nice.. I'll take a note just in case
(no release yet, just bumped version to snapshot)