clojurescript 2020-05-26

Eliraz09:05:23

Hey, I got a question with regards to clojure.spec can the spec code be omitted form the production js output? I mean, I don't want the JS to be bloated (or maybe it does not compile it to JS anyways?)

Oliver George09:05:41

Short answer is yes.

Oliver George09:05:52

I have two source paths. One just for spec code. I don’t include that in the paths for my advanced build.

Eliraz13:05:41

@olivergeorge Can you show an example to how you'd define those?

bhauman21:05:11

figwheel-main 0.2.6 has been released. This features a much nicer workflow for using NPM, I’ve started the docs for it here https://figwheel.org/docs/npm.html

Janne Sauvala08:05:42

That’s awesome work! Comparing now figwheel-main to shadow-cljs, is there any big differences between these two feature wise? I have been personally leaned towards using shadow-cljs because of the better npm-integration

bhauman12:05:45

I’m actually not the person to ask. 🙂

bhauman21:05:38

It supports extra-mains and autotesting. The docs are still in progress, I want them to really cover how this all works so there are very few gotchas

🎉 16

👍 4

thheller21:05:05

@bhauman this looks incorrect

{:none {"npx" "webpack" "--mode=development" :output-to "-o"
:final-output-to}}

bhauman21:05:29

@thheller in what way?

thheller21:05:40

I think thats supposed to be a vector?

bhauman21:05:50

oh yeah thanks!!!

bhauman21:05:55

doh

bhauman21:05:50

@thheller thanks for taking a look at it

bhauman21:05:51

commited the fix

👍 4

bhauman21:05:44

@thheller also I’m finally fixing dang devcards React require right now. I’m sorry you’ve had to field that question so often

👏 12

thheller21:05:41

sweet 🙂

bhauman00:05:42

well sablono needs to be updated as well

bhauman00:05:03

filing an issue

bhauman00:05:37

or perhaps its time to stop depending on sablono, but thats a bigger job ;(

bhauman12:05:48

that was wrong, sablono is fine. I was just getting a cached version of it

2020-05-26

Channels