Anyone got any advice on preventing cljsbuild from compiling certain source paths?

I have the following in my build configuration:

{:id           "dev-billygoat"
                         :source-paths ["src/billygoat/cljs"]
                         :figwheel true
                         :compiler     {:main                 billygoat.core
                                        :output-to            "resources/public/billygoat.js"
                                        :output-dir           "resources/public/out"
                                        :asset-path           "out"
                                        :source-map-timestamp true
                                        :verbose true}

The thing that's troubling me is that eg lein cljsbuild once dev-billygoat picks up files for another part of my project, from src/reagent, and overwrites part of the Reagent namespace when I'd like that not to happen.

Tried a couple of things but it feels like there's a bit too much "magic" happening in source path resolution.

@attentive cljsbuild adds all the source paths from all the builds to the classpath, if you want to use cljsbuild you will need to not have one namespace that does different things

Yes, I'm just figuring that out—I've never really tried to get it to do a bunch of orthogonal builds in one repo before

(the src/reagent directory contains shim redefinitions of core Reagent stuff for React Native, but I'm trying to package a vanilla Reagent application in the app as a WebView)

you can try to use leiningen profiles so that all teh paths aren’t in the project map at the same time

Yeah, I'm attempting that—I think if I move the src/reagent stuff to my React Native source paths (which have their own profile(s)), that may work—I think it's being included in both builds as part of a general principle of resolving deps via any local overrides (which is fine)

@mfikes Please, don't let your life be completed by this - enjoy and hack on! https://github.com/jafingerhut/clojure/tree/undefined-behavior

@andy.fingerhut Hah! That's awesome!

Dude, I am totally going to pimp this out.

🐸

Several more URLs I can think of.

great stuff, now I just need to compile this into a jar, drop it in a coworker's .m2 in place of the official clojure, and wait...

Is it possible to use npm modules required through :npm-deps in js modules? Things work as expected with webpack bundling, but we don't have the nice GCC optimizations there. Here's what'd work in my imaginary world:

build.edn:
  ...
  :npm-deps {:react "16.5.2" ...
  :foreign-libs {:file "src/js/components"
                 :module-type :es6} ...

src/js/components/some_component.js:
  import React from "react";
  ... React.createElement( ...

@aisamu GCC optimizations cannot work in general for JS libraries since they were not written with Closure mind

ClojureScript has it easier since we generate code for you

Is there a better way to add conditional style names?

newer versions of reagent allow a vector of strings

I am using 0.6.1

I never found a better way, you could write a function that does it or update

So I presume I use when-let to conj another one if current-items is greater than 3?

you coud use cond->

It's not a biggie, jsut thought about asking if there might be a better way

(cond-> "list-header" (> (count current-items) 3) (str " red"))

I think using cond-> with many conditions would result in a lot of extra str calls

sure

it seems like they just want a more readable way of doing their classes

I prefer the cond->

I don’t think you should be worrying about extra str calls

that’s not going to show up meaningfully in any profile of a React application

@tavistock the class vector of strings/keywords is pretty nice IMO, didn't know that worked