This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-23
Channels
- # babashka (68)
- # beginners (133)
- # calva (5)
- # chlorine-clover (21)
- # cider (40)
- # clj-kondo (42)
- # cljs-dev (31)
- # clojure (53)
- # clojure-austin (1)
- # clojure-europe (30)
- # clojure-italy (6)
- # clojure-nl (3)
- # clojure-uk (104)
- # clojurescript (15)
- # datascript (2)
- # datomic (50)
- # emacs (12)
- # fulcro (82)
- # graalvm (4)
- # hoplon (225)
- # jobs (4)
- # jobs-discuss (7)
- # joker (5)
- # juxt (17)
- # kaocha (13)
- # leiningen (16)
- # meander (21)
- # nrepl (18)
- # off-topic (16)
- # pathom (8)
- # pedestal (13)
- # perun (1)
- # re-frame (4)
- # spacemacs (23)
- # testing (28)
- # unrepl (3)
- # vim (5)
- # xtdb (1)
There are quite a few failures in Canary (https://github.com/cljs-oss/canary). I haven't yet had time to assess them.
@kommen I removed everything intentionally - but I'm ok w/ reverting the compile target bit for :graaljs
if you want to make a revert patch for that + a test that would be helpful
@mfikes they seem configuration oriented? though I have to say I'm not so familiar with the Canary output
in the long run, would you consider making compile targets pluggable, i.e a multimethod?
if you want to take that step so you can get this working w/o putting :graaljs
back in that would be best
so something along the lines as shadow does: https://github.com/thheller/shadow-cljs/blob/fda0dc02d8199d5475a3ab42a3d2fd247c237235/src/main/shadow/build.clj#L166-L182
@dnolen Yes, the failures seem to fall roughly into two categories. And I wouldn't be surprised if they are solvable in those downstream projects without changes in ClojureScript.
Truth be told, I did look at cljs-time
. It was referring to the Rhino REPL but not using it. Simple fix there.
I have multiple “xxx.js requires transpilation….“, like here https://travis-ci.org/github/binaryage/cljs-oops/builds/665810571#L1015
@darwin the requires transpilation stuff seems a bit strange - only would happen if you're loading :none
compiled stuff
thanks, looking into it my test js file is injected here by phantom: https://github.com/binaryage/cljs-oops/blob/master/test/resources/phantom.js#L39 and compiled from this config: https://github.com/binaryage/cljs-oops/blob/master/project.clj#L96
I think this is caused by phantom js runtime being too old. When I load the same file in normal browser, it works as expected. I’m going to rewrite the test runner to pupeteer to see if it fixes the issue…
just FYI, canary issues in my repos had two sources: 1) using phantom.js => fixed by switching to puppeteer 2) using goog.dependencies_
[1]
[1] https://github.com/binaryage/cljs-devtools/commit/8dd8b9c5d60c05d5ba5b60f2d908bb3eab8e2f8d