This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (5)
- # architecture (17)
- # aws (2)
- # bangalore-clj (1)
- # beginners (157)
- # boot (22)
- # boot-dev (2)
- # cider (64)
- # clara (2)
- # cljs-dev (3)
- # clojure (30)
- # clojure-art (2)
- # clojure-australia (1)
- # clojure-belgium (1)
- # clojure-denver (1)
- # clojure-dusseldorf (1)
- # clojure-europe (8)
- # clojure-finland (2)
- # clojure-italy (9)
- # clojure-nl (21)
- # clojure-spec (261)
- # clojure-switzerland (3)
- # clojure-uk (67)
- # clojurescript (57)
- # clojurewerkz (2)
- # cursive (3)
- # datomic (27)
- # emacs (12)
- # figwheel-main (2)
- # fulcro (48)
- # garden (67)
- # graphql (41)
- # jobs (8)
- # kaocha (8)
- # liberator (2)
- # lumo (1)
- # off-topic (19)
- # parinfer (9)
- # perun (4)
- # re-frame (50)
- # reagent (7)
- # remote-jobs (4)
- # ring-swagger (20)
- # rum (6)
- # shadow-cljs (170)
- # specter (3)
- # tools-deps (19)
- # vim (3)
I wonder how easy it is to add your own test runners for shadow-cljs, if e.g. I’d like to integrate Kaocha-CLJS, would it be possible? I’ve made an issue for Kaocha here: https://github.com/lambdaisland/kaocha-cljs/issues/2
I like the nice pretty-printed output of Kaocha for Clojure. The shadow test runner uses the default clojure.test reporting AFAICT?
I’ve never used Kaocha-CLJS, but it seems it’s connecting to a CLJS repl via a websocket and gets the results out, then pretty-prints via Clojure.
I have not used it any kaocha neither CLJ nor CLJS so I have no idea what even the goal is
Let me rephrase my X/Y problem then — how can I get a pretty diff when my shadow-ran CLJS test fails?
that doesn't have a cljs impl. we can't use that easily without a whole bunch of extra crap we don't really want when running tests
For sure. I’m just showing that library as an example of what a “pretty diff” looks like
I don’t have any strong preference on what should be the ideal pretty diff, but something that helps me narrow down the difference between two possible huge maps would be nice.
Yeah that’s what I’m after. Colors are nice, but secondary. Seems like I can just require that in my namespace and it’ll do the correct thing…
don't like that it messes with the internals of cljs.pprint but I guess yes you just require it
Doesn’t seem to work under node:
ERROR in (select-tag-simple) (TypeError:NaN:NaN) toggling a tag on and off works expected: (= true (gamma.state/tag-selected? selected-state tag-id1)) actual: #object[TypeError TypeError: Cannot read property 'append' of undefined]
Yeah I’ll keep hunting. Point taken about running tests against compiled builds — makes total sense.
problem with koacha will be that is directly interops with the cljs analyzer and compiler
that means that it won't understand any of the shadow-cljs features such as npm integration
dunno how hard porting deep-diff would be. probably pretty hard as pretty much all the libs used are CLJ only.
Seems to be a known issue: https://github.com/pjstadig/humane-test-output/issues/37
I’ll keep you posted — ideally this should be something that shadow doesn’t need to change to accommodate (though perhaps in the spirit of reasonable defaults, could provide out of the box if needed).
for the browser test target I already hooked up
cljs-test-display which is great
I’d actually prefer to run my tests on a browser, but node was the easiest to start with (to run unit tests in a very light weight manner). How do you run CLJS tests in CI? Headless chrome?
Ah, good to know. I’ll see how that looks like. Gotta run, thanks for everything (once more!)
I know hardly anything about how cljs works under the hood, so forgive me if this is a dumb question. I want to compile a cljs library into a single script file, load that file from a browser window into a script tag, and start using the library. Is that possible? Would I use shadow-cljs to do that?
shadow-cljs (and the regular CLJS compiler) supports something called module splitting
so you could, as part of your build, have your library built as one module and your application built as another module
but if you want to be able to distribute that pre-built library and use it in other builds external to your application, it won't work
What you're saying makes sense. Why it is so does not make sense. What I'm trying to do sounds really trivial (in my head, anyway), and we do it in JS all the time: write a script that attaches a useful function to some global var, run that script from the browser, then reference that global var. Why is that so hard in cljs?
the context matters though. how do you want to use it is the more important question?
Yeah, context will help. Are you guys familiar with hyperfiddle? http://www.hyperfiddle.net It's basically a fiddle environment that sits on Datomic - write a query, write a quick view in cljs, and boom - you have a scrappy little app running on datomic cloud somewhere. It already can load custom script tags, which makes it pretty easy to load vanilla js stuff, but I'd like to consume cljs libs from this environment.
I have a desire for this same kind of capability (different context, same use case). I explored it a few weeks ago and wasn't able to find a way to do it easily
the problem is that when your CLJS code is compiled, it bundles with it things like the CLJS data structures and google closure code, that is incompatible with other separate CLJS bundles
so e.g. two CLJS applications, built from separate projects, will have their own copies of the vector/map/etc. data types. which means that if you try and pass a vector from one bundle to the other, the data types won't be compatible. the thing you passed it to will treat it as a foreign JS object
there's definitely some interplay there. it's the way the CLJS compilation process works
what I would love is the ability to create a bundle that left out all of that stuff, and could be placed on a page with a foreign CLJS bundle. but when I asked dnolen about it, he said it wasn't supported at all
unfortunately for me, this was a fundamental requirement for the project I'm building. so what I ended up doing is serializing/deserializing the data across those bundle boundaries 😕
so the fundamental problem is that CLJS builds generally include all of
cljs.core and some of the google closure library
so even if you strip out cljs.core you still need access to the macros somehow when compiling your lib code
it sounds like hyperfiddle already has self-hosting. so if your library is self-host compatible, you might be able to do what you were saying where you load the file and
Self-hosting in hyperfiddle means running the backend services yourself. You're talking about the host language right?
there are ways to setup your project to use it though. it sounds like hyperfiddle already does, since it's executing your CLJS code in the browser
That will break down as soon as an external lib (like an npm lib) is referenced though, right?
honestly I would ask @dustingetz how he would try and do this 😛 he's building hyperfiddle
I was just chatting with him.His solution (and this sounds much more practical), is to just host hyperfiddle yourself, and include whatever deps you need at build time. I just wondered why we can't do what JS can do, which ya'll answered very well (thanks!)
we can do everything JS does. its not different really, JS has pretty much the same restrictions
just remember that you are not just using YOUR library. you are also using
cljs.core and some of the closure library
to compare with that a JS library assume that your JS lib wants to use
lodash or so
you just can't do jQuery style libs where everything assumes that there is a global
jQuery loaded somewhere
so, for my use case. I am building a dev tool that I want to allow people to extend with their own 3rd party plugins
would I be able to instruct people building those plugins how to build their CLJS code in a way that could interface with my main dev tool application?
cause right now, the solution I have is to communicate via stringified-EDN or transit and hand them a DOM node to render their plugin to 😕
@lilactown not sure I understand but no you cannot pass CLJS collection instances between different
would I be able to instruct people building those plugins how to build their CLJS code in a way that could use my application's version of
OK, I'll have to think on that. there will be times that this lives on the same page as a user's application at development time, so I also need to make sure I don't clobber their application's
problem is ensuring the library code uses the same version of everything your code uses
with shadow-cljs, would
:output-wrapper be able to ensure I don't clobber a user's application?
there's 3 types of things that might be living on the page: - user's application - REBL application - 3rd party REBL viewers
well. right now, I'm compiling the REBL application and keeping it to one module. so it should be isolated
what I'm trying to figure out now is how the 3rd party REBL viewers will hook into the REBL application
not sure how that would work in a REBL style application given its protocol heavy nature
atm, the user installs a library in their application code that handles serializing and sending data to the REBL application, and listening for events and calling
in my testing I haven't noticed any real perf problems. but I've yet to use it in really complex applications
the way it works right now is that when you want to send something to the REBL app, you
the library the user installed, adds a tap listener that adds the data as an entry to a global atom and sends it over the wire for viewing with an ID that it can use to reference the entry in the atom