Fork me on GitHub
#clojurescript
<
2017-06-24
>
pastafari07:06:13

Folks, has anyone tried using jsdom as a dummy dom for testing in cljs?

pesterhazy09:06:19

@emccue you can just use both and run the two servers on different ports

dnolen15:06:03

@pastafari I haven’t used it with CLJS but I have used it before. I don’t forsee any issues if you can use it as foreign lib.

pastafari15:06:58

@dnolen yep i figured. Will try and wrap my head around using it as a foreign lib.

dnolen15:06:00

@pastafari oh this is under Node.js and you don’t need advanced

dnolen15:06:08

you don’t need to bother with foreign libs

dnolen15:06:30

just npm install jsdom and (js/require "jsdom") and be on your merry way

pastafari15:06:07

@dnolen i’ll give it a shot! Thanks 🙂

dnolen15:06:14

will probably cut a ClojureScript release on Monday, if you know how to test against master try to give it shot if you can

zilti18:06:20

<!! is not available on core.async for clojurescript, right?

zilti18:06:47

Hmm. Is there an alternative?

metametadata18:06:02

@zilti it's possible to implement, but it goes against the good practices, there's only a single thread in JS and you're not encouraged to block it

pesterhazy19:06:04

@metametadata not encouraged? I don't understand. What would be the point of blocking in javascript? While you're blocking nothing interesting will happen, right?

dnolen20:06:38

@zilti no alternatives, you can't really block in JS userland

sh3rawi23:06:53

is it weird that if i use the same opts for compiling a project when directly calling java -cp on a .clj file with calls to the build api directly, against using lein cljsbuild, i do not get the exact same js file ?