This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-15
Channels
- # beginners (56)
- # boot (4)
- # cider (22)
- # clara (10)
- # cljs-dev (50)
- # cljsrn (27)
- # clojure (27)
- # clojure-conj (4)
- # clojure-dev (3)
- # clojure-italy (17)
- # clojure-nl (12)
- # clojure-norway (3)
- # clojure-spec (10)
- # clojure-uk (137)
- # clojurescript (132)
- # cursive (4)
- # datascript (2)
- # datomic (109)
- # devcards (2)
- # editors (1)
- # emacs (4)
- # euroclojure (2)
- # events (4)
- # figwheel (1)
- # fulcro (15)
- # jobs (1)
- # jobs-discuss (4)
- # juxt (3)
- # leiningen (2)
- # off-topic (21)
- # onyx (13)
- # other-languages (8)
- # pedestal (6)
- # re-frame (22)
- # reagent (5)
- # reitit (1)
- # ring-swagger (3)
- # shadow-cljs (75)
- # sql (6)
- # tools-deps (2)
- # vim (1)
- # yada (8)
https://dev.clojure.org/jira/browse/CLJS-2778 may need to be looked at prior to release (at least to decide if it is a non-issue)
Looking at the change, the test case should be fixed to use goog.global["ReactDOMServer"]
There is also https://dev.clojure.org/jira/browse/CLJS-2779, which may in fact be related to the same underlying root issue
I had started drafting this compilation of relevant doc PRs
https://gist.github.com/mfikes/b457cb5d850af87d5047d1ac0c99c6d6
The Git Deps revision to the :aot-cache
docs isn't yet relevant (because it is currently disabled until we figure out https://dev.clojure.org/jira/browse/CLJS-2765)
As an aside, I've been wondering if using some sort of label like "next release" would be easier to manage for clojurescript-site
PRs that are pending a ClojureScript release.
Yes, Canary is still running. The only failure in last night's run was closure-latest
which was CLJS-2765. That particular project is currently running here https://travis-ci.org/mfikes/closure-latest
Minor puncation pr to webpack guide: https://github.com/clojure/clojurescript-site/pull/239
I'm updating https://github.com/clojure/clojurescript-site/pull/231 for another round of reviews
@mfikes sorry maybe I’m missing something - does that failure require us to do anything?
btw. current canary jobs can be also viewed from commit list in “jobs” branch via github: https://github.com/cljs-oss/canary/commits/jobs
Canary is green across the board now https://github.com/cljs-oss/canary
@pesterhazy thanks fixed in my PR now
@mfikes I just pushed the webpack guide, let me know when the other ones are ready and I can review and then we can announce on the various channels
Definitely make sure to mention the externs inference fixes and link to the new guide on using Webpack
Here is a "live" link to the news post https://github.com/clojure/clojurescript-site/blob/mid-2018-release/content/news/2018-06-15-release.adoc I'm thinking of (apart from any general copy edits for correctness and checking that the Contributors list is correct), adding the stuff David just mentioned above
312 post looks good, I think improved externs inference + :global-exports
is the big story 🙂
I'm not sure what copy to add for externs inference + :global-exports
. I've added a sub section https://github.com/clojure/clojurescript-site/blob/mid-2018-release/content/news/2018-06-15-release.adoc#improved-externs-inference
Is this tied to https://clojurescript.org/guides/webpack ?
do you all have guidance for when to use the webpack-bundle approach versus individually including npm dependencies and trying to get externs to work one by one?
Cool. https://github.com/clojure/clojurescript-site/pull/231 might be ready unless anyone sees any changes needed
@dnolen Right. They are essentially documentation to accommodate patches in tickets that haven't yet been merged. (Perhaps if we add new labels there could be a label to mark things
Hah! ClojureScript News is now almost 1 year old. https://clojurescript.org/news/2017-06-26-welcome