Can you try after doing an npm install platform

or maybe "platform" :as platform

I'm just guessing here, not too sure about it

Well, the dependency is in the kaocha source somwhere (funnel client from the looks of it) so I can’t change the require. But I’ll try npm installing it

shadow automatically picks up npm modules, I'm not sure how it will work with figwheel though

Ok, so npm install platform gave me a new error. Then I did npm install stacktrace-js, and now figwheel compiles successfully. Those should probably be mentioned in the installation docs?

Now I have a bunch of runtime errors:

@U9MKYDN4Q did you find this repo? it contains a complete working example of kaocha-cljs2 https://github.com/plexus/cljs-test-example

these are the npm packages we install, agreed that this should be documented: https://github.com/plexus/cljs-test-example/blob/main/shadow-browser-kaocha-cljs2/package.json

thanks, will have a look later!

I only followed the kaocha-cljs2 readme

Doc PRs would be super welcome, we never had the chance to properly polish this stuff up. I recently started this example repo so at a minimum people can look at a fully working example and copy bits over.

I’ll see what I can do if I manage to get it running

note that funnel-client has a deps.cljs which mentions platform, so depending on your cljs build tooling that should get pulled in automatically

and stacktrace-js / stack-trace are in the deps.cljs of chui-core

they didn’t

I’m using figwheel, with what I imagine is pretty vanilla config

You're in unexplored territory then. Adding : install-deps true to your cljs config may help

Adding that installed the deps for me, but I still have runtime errors when I run the build.

I looked at the example repo. I see all the examples use shadow-cljs. I don’t know anything about shadow, so translating to my setup will involve rabbit holing into shadow which is a little out of scope right now 😅

yeah, there's a lot of details to be figured out when trying to get it to run with a specific tool. So far we've focused on shadow-cljs because kaocha-cljs2 was created with shadow in mind, the approach for kaocha-cljs does not work for shadow. If you have a fairly vanilla clojure compiler setup than kaocha-cljs might be a better fit, it's still supported, we use it on several projects as well.

oh, ok

The plan is to expand that repo with more examples, there's a lot of permutations of tool x runtime, I'll see if I can get a figwheel example going next

I completely understand 😅

I guess the “2” made me think it superseded the other one, that’s why redirected from kaocha-cljs to kaocha-cljs2

yeah, understandable. It is meant as a successor, it fixes some things that we can't fix in kaocha-cljs, but at the cost of a lot of additional complexity. Kaocha-cljs does not work for everyone, but if it works it's much easier to get going.