shadow-cljs does not depend on zprint no, never has

do you actually use shadow-cljs.edn to manage deps? or rather deps.edn/project.clj?

shadow-cljs info doesn't work well for those cases

could also be stuff injected by your editor if your editor is starting it? e.g. emacs jack-in

*correction: shadow-cljs info does show it as a direct dependency, but it’s not in shadow-cljs.edn

I do use it for managing deps (although there’s a deps.edn as well in the same dir, for clj dependencies, so unrelated)

and I start shadow-cljs manually from terminal, so it’s not that either

dunno where it would come from other than one of your other dependencies

can you send the .shadow-cljs/classpath.edn?

that contains all the raw classpath data, maybe info just doesn't construct it correctly

will privmsg if that’s ok

sure, or email <mailto:[email protected]|[email protected]>

hm i just realized that I have a zprint alias in my ~/.clojure/deps.edn ... could that be it?

{:aliases {:zprint {:extra-deps {org.clojure/clojure {:mvn/version "1.9.0"},
                                 zprint/zprint       {:mvn/version "1.0.2"}},
                    :main-opts  ["-m" "zprint.main"]}
           :with-datomic-valcache {:jvm-opts ["-Ddatomic.valcachePath=/Users/nathell/.datomic-valcache/"
                                              "-Ddatomic.valcacheMaxGb=1"]}
           :rebel  {:extra-deps {com.bhauman/rebel-readline {:mvn/version "0.1.4"}}
                    :main-opts  ["-e" "(do (require 'nrepl.server) (require 'cider.nrepl) (nrepl.server/start-server :port 7777 :handler cider.nrepl/cider-nrepl-handler) (println \"Started nREPL at port 7777\"))" "-m" "rebel-readline.main"]}
           :prof   {:extra-deps {com.clojure-goes-fast/clj-async-profiler {:mvn/version "1.0.3"}}
                    :jvm-opts   ["-Djdk.attach.allowAttachSelf" "-XX:+UnlockDiagnosticVMOptions" "-XX:+DebugNonSafepoints"]}}
 :deps    {cider/cider-nrepl          {:mvn/version "0.30.0"}
           org.clojure/clojure        {:mvn/version "1.10.1"}
           vvvvalvalval/scope-capture {:mvn/version "0.3.2"}}}

fwiw (tap> (edn/read-string (slurp ".shadow-cljs/classpath.edn")) with (require '[clojure.edn :as edn]) in via npx shadow-cljs clj-repl and then look at in

gives me

#{[rewrite-clj "0.6.1" :exclusions [[com.cemerick/austin]]]
  [borkdude/edamame "0.0.11-alpha.12"]
  [rewrite-cljs "0.4.5" :exclusions [[org.clojure/clojurescript]]]}

under the :deps-resolved key

yup I was wrong originally, sorry > *correction: shadow-cljs info does show it as a direct dependency, but it’s not in shadow-cljs.edn (edited)

wait nvm, that are the deps of zprint 😛

its re-frame-10x

#{[superstructor/re-highlight "1.1.0"]
  [cljsjs/highlight "10.3.1-0"]
  [com.yahoo.platform.yui/yuicompressor
   "2.4.8"
   :exclusions
   [[rhino/js]]]
  [zprint "1.0.1"]}

ah ha!

thanks!

i guess the q remains why it’s listing it as a top-level dep, but minor

thanks Thomas, you’re a star! i’ve just started sponsoring you on github, it’s long overdue 🙂

thanks, happy to help 🙂

[day8.re-frame/re-frame-10x "1.2.2" :exclusions [[com.cognitect/transit-java] [org.clojure/clojure] [thheller/shadow-cljs] [org.clojure/clojurescript] [com.cognitect/transit-clj] [org.clojure/core.async]]]
  [cljsjs/highlight "10.3.1-0"]
  [com.yahoo.platform.yui/yuicompressor "2.4.8" :exclusions [[rhino/js]]]
  [superstructor/re-highlight "1.1.0"]
  [zprint "1.0.1"]
    [borkdude/edamame "0.0.11-alpha.12"]
    [rewrite-clj "0.6.1" :exclusions [[com.cemerick/austin]]]
    [rewrite-cljs "0.4.5" :exclusions [[org.clojure/clojurescript]]]

doesn't print as top lvl for me? using your snapshot?

i’m getting

hmm thats a different version?

maybe you have something in ~/.shadow-cljs/config.edn?

just cider-nrepl

odd

i did bump re-frame-10x and the warnings went away, though

yeah you had some pretty old stuff in there

ah that info is after I bumped it 🙂

me being the source of confusion again

thanks!

what kind of file is that? why is that on the classpath?

can you link me to the instructions for the package? why did you have to download it?

That's the API file, supplied by Tableau that I'm trying to integrate into my app. It's a plain JS file that I downloaded because I thought I needed it locally to include it in my build.

It is available via a CDN if that's an option.

sorry but "JS file" is very very very broad definition, so I need more details

if this is intended to be included separately you do no include it via the build at all

just like a CDN build

you just put it into your public/vendor or so dir

then in HTML <script src="/vendor/tableau.embedding.3.3.0.js"></script>

(assuming public is the folder used for your webserver)

Ok, that sounds promising. I thought I needed the source locally to be able to reference classes included in the file, but it sounds like I just need to load the script in my app and then just do the old-fashioned js/TableauViz kind of thing.

I don't have the slightest clue what this is or does, so can't comment on that

but if its an intended "CDN" type library, then it is likely not meant to be "consumed" by other build tools such as shadow-cljs

as in it is already standalone and fully bundled

Well, you've at least challenged my assumptions, so I have some more directions I can explore. That's what I needed to know, thanks!

I don't have much experience working in the "raw" ES6 ecosphere, and I'm also new to shadow-cljs, so it's easy for me to get lost.

basically you always follow the instructions given by the library, and if they give you some import statements you are supposed to do then you can reference https://shadow-cljs.github.io/docs/UsersGuide.html#_using_npm_packages which has a bunch of translation examples

👍 Thanks!

if no such instructions are given and just a CDN reference with a script tag then you do that and don't tell your build about it at all 😛

It does have "import" statements in the docs, but they weren't working because the library isn't an NPM package (got an error about the imported classes not being present in node_modules). But we'll see how far I get with the JS globals. At least it's building successfully now.

do you have a link for me?

I'm upgrading from an earlier, non-ES6 version of the API, so I'm following the instructions here: https://help.tableau.com/current/api/embedding_api/en-us/docs/embedding_api_migration_guide.html

ah ok, so it is an ES module. then the require should have been fine

but possible that the file includes something the closure compiler doesn't unterstand

so could be that the script tag is the better option, if its sufficient

Sounds good, I'll pursue that.