This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-07
Channels
- # beginners (71)
- # boot (25)
- # cider (204)
- # clara (18)
- # cljs-dev (10)
- # cljsrn (64)
- # clojure (50)
- # clojure-dev (2)
- # clojure-dusseldorf (1)
- # clojure-india (5)
- # clojure-italy (1)
- # clojure-nl (21)
- # clojure-poland (65)
- # clojure-spec (41)
- # clojure-uk (10)
- # clojurescript (4)
- # core-async (5)
- # cursive (2)
- # datomic (17)
- # duct (8)
- # emacs (8)
- # fulcro (1)
- # graphql (21)
- # hoplon (2)
- # javascript (3)
- # lumo (25)
- # mount (5)
- # off-topic (5)
- # onyx (3)
- # portkey (6)
- # re-frame (15)
- # reagent (5)
- # rum (1)
- # shadow-cljs (198)
- # spacemacs (19)
- # specter (2)
Thanks. When this one is ultimately ready (if it is good), then I can get Canary to test against the latest Closure Library: https://dev.clojure.org/jira/browse/CLJS-2703
(This only arises as an issue for Canary testing because the repo I'm using happens to have a hyphen in its name: https://github.com/mfikes/closure-latest)
I have to say that itβs really impressive that GraalVM performs better on the JS benchmarks than Nashorn
is there a way to increase the timeout in Canary? Lumo builds now test against 3 versions of node and therefore take forever: https://travis-ci.org/anmonteiro/lumo/builds/376085593