This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-19
Channels
- # announcements (37)
- # aws (6)
- # babashka (12)
- # babashka-sci-dev (16)
- # beginners (83)
- # biff (10)
- # cider (14)
- # cljdoc (26)
- # cljs-dev (20)
- # clojure (123)
- # clojure-czech (9)
- # clojure-europe (26)
- # clojure-nl (4)
- # clojure-norway (20)
- # clojure-spec (7)
- # clojure-uk (6)
- # clojured (14)
- # clojurescript (28)
- # cursive (5)
- # datalevin (8)
- # datomic (3)
- # duct (6)
- # emacs (26)
- # events (2)
- # fulcro (7)
- # gratitude (1)
- # holy-lambda (19)
- # integrant (1)
- # jobs (2)
- # leiningen (8)
- # lsp (7)
- # nyc (1)
- # pathom (70)
- # re-frame (8)
- # reagent (15)
- # releases (1)
- # sci (8)
- # shadow-cljs (117)
- # testing (5)
- # tools-deps (11)
- # vim (5)
oh oh https://github.com/google/closure-compiler/commit/91aeeab2ab6fa38186a17867710210ef06719dcf
just a test for now but given the commit comment looks like they are moving to min java11
hrm, though I guess it is 8 years old, I do think a significant number of users have moved on, though I don't think this is captured in the survey? Maybe @alexmiller knows
you're asking about jvm version usage?
(answers are multi-select)
OTOH, the JVM usage in CLJS is at build time, it's not the same as running with JVM in production
https://clojure.atlassian.net/browse/CLJS-2820 describes an issue w/ using cljs.loader
in a project that doesn't use :modules
. cljs.loader
isn't compiled to javascript unless the compiler options include :modules
. I have a project that would benefit from being compiled with or without code splitting depending on the deployment environment, and compiling cljs.loader
when not using modules is necessary to support that. This requires a couple minor changes to cljs.closure/compile-loader
. I'd like to submit a patch for that. Any thoughts/things I should be aware of before submitting that?
@alexmiller thanks!
I added a patch on https://clojure.atlassian.net/browse/CLJS-2820 and am attempting to follow the directions at https://clojure.org/dev/developing_patches but I don't see the "edit" button in Jira. I'm unsure if I'm just missing it or if I need to be given permission to edit tickets.
hey Tom, I can help with that
seems like you've signed the CA, have an account, and are in the right groups
to edit you just click blindly anywhere in the description
then it becomes editable and there are save/cancel buttons at the bottom
Hi Alex, thanks for the help. I'm trying to do the "Mark the ticket as having a patch ready for screening by editing the Patch field" part from the guide on http://clojure.org, but even after clicking into the description area I don't see a heading "Patch" or anything like that. Could be Jira's terrible UI, but I'd hesitate to rule out my own incompetence.
ah, there is a Patch field but it might be buried under "More fields" in the right side bar