Fork me on GitHub
#shadow-cljs
<
2021-02-13
>
bringe01:02:14

Does anyone here happen to know how to make the typescript compiler not complain about imports like import { some_thing } from 'goog:some.ns' ? I've done some searching but haven't found a solution.

william14:02:53

can :dev {:compiler-options {:invalid-arithmetic false}} in shadow-cljs.edn silence a warning coming from a dependency?

thheller16:02:59

no, but yes đŸ˜‰

đŸ˜‚ 3
thheller16:02:12

:dev {:compiler-options {:warnings {:invalid-arithmetic false}}} can

william17:02:27

thanks, you're the best đŸ™Œ

mauricio.szabo20:02:12

@thheller Hi there. It seems that recent versions of Shadow-CLJS do not work with OpenJ9 JVM. Do you know if it's a ClojureScript issue, or a Shadow-CLJS one? It does compile, but when I try to run the JS output it gives an error of ReferenceError: ...... is not defined. This ...... can be almost anything, but most of the time is key, $coll, $seq or something like this. I'm not really asking to solve it, but maybe you can have some insight on where the problem is :thinking_face:

thheller20:02:03

sounds like https://github.com/thheller/shadow-cljs/issues/804. not a clue what is happening or even how.

thheller20:02:05

there is no code in shadow-cljs or CLJS I'm aware of that prepends a $ to a symbol

thheller20:02:10

append yes, prepend no

mauricio.szabo20:02:39

Well, I remember a bug I had on a Clojure code with OpenJ9 that it resolved java methods to different implementations (for example, where both have the signature (int, int) or (long, long), or something). Maybe that's related? I remember that the method was resolved using reflection...

mauricio.szabo20:02:03

Seems like an interesting thing to investigate đŸ˜„

thheller20:02:31

yeah not a clue where to even start

thheller21:02:06

if you have a reliable way to reproduce the problem I'd be happy to check it out

thheller21:02:33

but the "random" nature makes this difficult

dpsutton21:02:45

i think alex might have made a ticket about this. method resolution is basically random and there might be problems with Clojure before any cljs gets involved on j9

william22:02:51

general question: how do you run automatically your tests from cider+shadow-cljs? I see by googling that in the past we didn't have an automated process, but I wonder if that changed

william22:02:04

I added:

:test {:target    :node-test
                       :output-to "out/node-tests.js"
                       :autorun   true}
to the configuration but nothing ever happens, and I don't know how to activate them