Tried converting a big reagent app to use the bundle target and webpack, it seems to work fine locally but production build takes a very long time (from 90 seconds to 16minutes) and some cljsjs deps didn’t work in the advanced compiled output… I should probably just upgrade all the cljsjs deps to their npm versions and not mix npm/cljsjs

I'm following the [Krell reagent tutorial](https://github.com/vouch-opensource/krell/wiki/Reagent-Tutorial), but running clj -m krell.main -co build.edn -c -r I'm getting compiler/analyzer exceptions because it can't find react-dom

should I install react-dom just to satisfy that dependency (even though I imagine it won't be used), or is there a way to not have it compile reagent.dom?

ah I think I missed a step

yay! @dnolen I did have to add a :paths ["src"] to deps.edn, I think that should be updated in the tutorial?

@plexus strange, I thought that’s the default in deps

maybe it's a red herring... it wasn't finding awesome_project/core.cljs, when I added it it did

it’s at least there on my system by default

~/d/testdeps ❯❯❯ echo "{}" > deps.edn
~/d/testdeps ❯❯❯ clojure -Spath
src:/Users/mk/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar:/Users/mk/.m2/repository/org/clojure/spec.alpha/0.2.176/spec.alpha-0.2.176.jar:/Users/mk/.m2/repository/org/clojure/core.specs.alpha/0.2.44/core.specs.alpha-0.2.44.jar

@plexus nice!

yeah :paths should be set for you, and I haven't heard about that one before from others

Yes for me too, src is default included in path without to specify in deps.edn...strange for you @plexus

That's been the default since very early.

since always

Is it possible to get webpack tree shaking for a project I'm importing into a cljs project?

Specifically, I maintain a react component lib at work, and I'd like to import some of those components into a cljs project.

@brandon149 what is your CLJS project using to build?

I'm using shadow-cljs

shadow-cljs will only include the JS files that you require

I'm not married to it, it's just what I'm most familiar with

wait, really?

yep

In that case, I need to double check some stuff

so if you require your JS components in a cljs namespace like:

(ns my-app.feature
  (:require ["component-lib/Foo" :as Foo])) 

this is assuming some things, like you’re deploying your component library as either CommonJS or ESM

ah, right now I require the whole lib and the final bundle is massive

yeah, this is a common question with component libraries like material-ui

you can see the example of how to fix this here: https://github.com/thheller/shadow-cljs/issues/412

I’m not sure how your component library is structured, but the idea is that you want to require just the files that you need and shadow-cljs will handle the rest

I never intended it to be consumed by non-js libs, so hopefully it works out 😅

Thanks-a-million

sure thing