Also why I was hoping for suggestions on things to look for or places to explore. It's a react component. And if I copy the code out of node_modules and into my source (require '["/name.js" :as n :refer (Component)]) gives me the same result. Their code comes in both es and cjs versions, the cjs seems to load, but shadow throws an exception when I try to require the es version directly.

I would console.log the object, and see if the Component is in object

right now it’s hard to tell what you’re experiencing

you should be able to see a key :Component in the #js {…}

(using console.log here might be better than e.g. println)

you should be able to do something like: (.-Component n)

and see the component you’re trying to :refer to

if it’s just not there, I don’t know. I’d have to look at the code. there might be some other documentation they have on how to import that might be more illuminating

e.g. it might be in some submodule "basicchart/BasicChart" or if it’s using the ES module it might be behind a default key

Yea, I tried the console.dir and looked, the component isn't there. I tried their example code. It was JSX, so I put it through babe and added that code into my project. No dice there either.

how do they import it in their example code?

I wasn't sure if maybe their code didn't get along with the closure compiler, or if there was something with that exception shadow was throwing.

sounds like their docs are just wrong?

unfortunately I can’t really help you without more information

Yea, I figured it was a long shot. If it was my code I'd just share it.

The shadow exception is just Exception in thread "async-thread-macro-9" java.lang.RuntimeException: java.lang.Exception: Not supported: class clojure.lang.ExceptionInfo

And seems to complain about transit things in the stacktrace.

go ahead and post the whole stacktrace

this only shows up when compiling with this require?

Only when compiling the es version of their package code placed directly into my source path.

but not with the cjs version

i’m not sure how shadow-cljs treats JS files on the classpath tbh. I think it might do some special things for node_modules that it might not do for normal JS on the classpath

Correct, just the es, not the cjs version.

Yea, was mostly just trying to get datapoints, hoping to find a clue.

Thanks for trying to help @lilactown, I appreciate you taking the time.

@grant do you have the full exception trace? ... 20 more seems top be cutting of the relevant parts?

as for the JS object see https://shadow-cljs.github.io/docs/UsersGuide.html#_about_default_exports

(js/console.dir x) is probably the most useful thing. I've seen JS packages that only have one default export and add properties onto that

so if the object has a default property you might find what you are looking for there

I have extra-dependencies specified in a deps.edn alias that I only want pulled in for a :dev build, how can this be done?

you can't

well you could with just clj

clj -A:foo shadow.cljs.devtools.cli watch app

oh okay, would you consider a feature request for such a mapping to be specified in the shadow-cljs.edn file?

something like {:builds {:dev {:deps/aliases [:dev] ...} ...}}

oh I forgot. you can also do shadow-cljs -A:foo watch app

via the config is not an option no

you should not have a build named :dev

that is not how it works in shadow-cljs

oh.. why not? From what I understood builds can be used as a way to pull in dev dependencies and additional source paths/compiler optimizations

no builds can not affect anything classpath related

compiler options yes but nothing that affects dependencies or source paths

the classpath applies to the entire started JVM

so if you run 2 builds and both would like different dependencies that wouldn't work

that being said you can do all of this via clj directly

oh right, because you can start multiple builds on a single server

thanks for clearing that up :)

@thheller I am trying to figure out a good way to get the full stack trace. I am seeing it on the console output of the terminal running npx shadow-cljs server. I'm triggering it by doing the (require ...) in the browser based repl that server provides.

try with shadow-cljs browser-repl instead, the web interface might not route some output properly maybe

Hi, can I point to different lein configurations in different builds, for example in test build I want to include more dependancies

The actual problem is not being able to use test check generators when connecting to nrepl started by shadow watch test

getting the following error:

(gen/generate (s/gen ::open?))
Error: Var clojure.test.check.generators/simple-type-printable does not exist, clojure.test.check.generators never required

did you require clojure.test.check.generators?

yes I did

in the repl

so from one terminal window I ran shadow-cljs watch test

Hi! I’m having some trouble getting my dev setup going - I’m trying to use httpkit and compojure on the server side and shadow-cljs for all the javascript. Thanks to help from @isak yesterday, I got changes to my reagent components live-reloading in the browser. However I can’t seem to get changes to the .css file to reload.

and from the other shadow-cljs cljs-repl test

I do have

:devtools {:after-load alexandria.core/mount-root
                            :http-root "/"
                            }

/ is definitely not correct

I’ve played with what to put in :http-root

it should be the path to your http root directory

My compojure routes are serving out of /public

/public?

you mean public in your project dir?

Yes, sorry for being unclear

shadow-cljs is compiling to /public/js/ in my project dir, that seems to reload well

The css file is in /public/css/, it also loads fine from the browser.

please be careful in your use of /

do you actually mean /?

I’m all ears

your absolute file system root?

Nope, I certainly don’t mean that

the path are relative to your project root UNLESS you start them with /

so it most certainly should be :watch-dir "public"

:http-root does nothing if you don't actually use that webserver

OK

changed {:http-root "public"} to {:watch-dir "public"} but still no joy

Reloads changes to the cljs files but not to the css file.

and the css file is in public/css/foo.css with your css file included in the HTML via <link rel="stylesheet" href="/css/foo.css">?

Yes

[email protected]: ~/dev/terrapin/alexandria $> ls public/css
total 8
drwxr-xr-x  3 rodfrey  staff    96B Jun 11 16:11 .
drwxr-xr-x  5 rodfrey  staff   160B Jun 11 16:16 ..
-rw-r--r--  1 rodfrey  staff    74B Jun 12 08:43 alexandria.min.css

<html>
  <head>
    <script src="/js/main.js"></script>
    <script src=""></script>
    <link rel="stylesheet" type="text/css" href=""></link>
    <link rel="stylesheet" type="text/css" href="/css/alexandria.min.css"></link>
    <meta charset="utf8" />
    <title>Alexandria</title>
  </head>
  <body>
    <div id="app">Hello from Alexandria dsf</div>
    <script>alexandria.core.init()</script>
  </body>
</html>

looks fine

Here’s the actual build definition, perhaps I did something boneheaded

{:source-paths ["src/cljs"]

  :dependencies [[bidi "2.1.6"]
                 [cider/cider-nrepl "0.22.0-beta1"]
                 [cljs-ajax "0.8.0"]
                 [com.andrewmcveigh/cljs-time "0.5.2"]
                 [kibu/pushy "0.3.8"]
                 [re-frame "0.10.6"]
                 [reagent-utils "0.3.3"]
                 [day8.re-frame/http-fx "0.1.6"]
                 [refactor-nrepl "2.4.0"]
                 [reagent "0.8.1"]]

  :builds {:alexandria {:target :browser
                 :output-dir "public/js"
                 :asset-path "/js"
                 :modules {:main {:entries [alexandria.core]}}
                 :devtools {:after-load alexandria.core/mount-root
                            :watch-dir "public"
                            }
                 }}

  :nrepl { :port 8777 }

looks fine

Bah

Restarted shadow-cljs server after changing to watch-dir and it works now

Sorry to bother you! But thanks for the help!

By the way, I love this system. I’ve actually been able to build up my shadow-cljs.edn and deps.edn from scratch and understand it all. I was never able to do that with lein or figwheel. Thanks for your work.

which says more about me than it does about either lein or figwheel, but there it is.

not really. I couldn't do that either 😛