I am trying to figure out why a dependency did not get pulled into a shadow build. I am weak on CLJS builds I will confess. FWIW, I started from the coolio Helix todo-mvc project: https://github.com/lilactown/helix-todo-mvc, That just does npm i and npm start to get things running: { "private": true, "scripts": { "start": "npx shadow-cljs watch app" <===================== }, "dependencies": { "react": "^16.13.1", "react-dom": "^16.13.1", "react-refresh": "^0.8.1", "react-router-dom": "^5.1.2", "react-slider": "^1.3.1", "shadow-cljs": "^2.8.94", "todomvc-app-css": "^2.4.1", "todomvc-common": "^1.0.5" } } My deps.edn is

{:paths ["src" "src/demo" "src/mxreact"]
 :deps {lilactown/helix {:mvn/version "0.1.1"}
        binaryage/devtools {:mvn/version "0.9.7"}
        thheller/shadow-cljs {:mvn/version "2.15.1"}
        tiltontec/matrix {:mvn/version "4.1.7-SNAPSHOT"}
        cljs-http/cljs-http {:mvn/version "0.1.46"}}}

;; shadow-cljs configuration
{:deps true
 :builds
 {:app {:target :browser
        :output-dir "js"
        :asset-path "/js"
        :modules {:app {:entries [app.core]}}
        :devtools {:http-root    "."
                   :http-port    8888
                   :reload-strategy :full
                   :preloads     [devtools.preload
                                  demo.dev]}}}}

(ns app.core
  (:require
    [tiltontec.model.core :as md]
    [react]
    [mxreact.mxreact :as mxr]
    ["react-dom" :as rdom]
    [demo.demo :as dmo]
    ["react-slider" :default ReactSlider]
    [tutorial.x100-hello-world.lesson :as app]
    ))

@hiskennyness shadow-cljs does not control what clojure does. if you set :deps true when running shadow-cljs watch app it will call clojure -M -m shadow.cljs.devtools.cli watch app and let clojure handle all dependency resolution and classpath creation. shadow-cljs will not attempt to download anything itself in that case. I do not know why it may not download something. In general I'd stay very far away from SNAPSHOT dependencies and instead use :local/root or :git/url if you can

did you maybe not restart shadow-cljs after adding the dependency? modifying deps.edn does require a shadow-cljs restart. just leaving the watch running won't work.

Good morning folks, I'm looking to set up a workflow where i have a shadow-cljs build running on a remote server and I connect to it from my local Emacs + Cider. Has anyone tried this?

hello 👋 I'm getting this error while trying to import an npm package

shared.js:1552 TypeError: Super expression must either be null or a function, not undefined
    at eval (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:35)
    at eval (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:35)
    at Object.eval (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:44)
    at r (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:2)
    at Object.eval (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:32)
    at r (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:2)
    at eval (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:4)
    at eval (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:4)
    at eval (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:1)
    at Object.shadow$provide.module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min (module$node_modules$react_leaflet_vectorgrid$dist$react_leaflet_vectorgrid_min.js:2)

Hello. How do I access a custom value provided in :compiler-options inside of (defmacro ...)? Say, I have {:compiler-options {:xyz "23"}}. What is the path to "23" in &env?

see https://github.com/binaryage/cljs-devtools/blob/master/src/lib/devtools/prefs.clj#L8-L12

@cljs.env/*compiler* :options is basically :compiler-options from your build config

No, @thheller, I did not have a watch running. The npm start command indirectly starts a watch, but I control-c'ed it each time, once it announced the missing dependency. Yes, I have :deps true in my shadow-cljs.edn, I am surprised to hear SNAPSHOT is a bad idea. Is that not a standard part of the ecosystem? I have noticed they do not work as dynamically as is really needed for iterative devlopment.This could be a breakthru! 🙂 I never heard of :local/root or :git/url options. To what are those options? I'll look around. I will also see what the clojure CLI crew has to say about dependency resolution. Thx!

both :local/root and :git/url are tools.deps options

note that running npm start does not imply that there is not a previous running server

eg. having it running twice in separate terminals for examples

so make sure that on startup it doesn't say "connected to server"

if it does that you do have an active server running

I am getting a "required namespace is not available error" when starting up shadow-cljs. I created a project with a hyphen in it's name but then my main function is contact-book.core/main which I can't call in my index.html script because js does not allow hyphens. Am I understanding that correctly? Wherever my main function is should not have a hyphenated namespace or am I doing something else wrong?

Can 'dev-http' start up an https server? https://shadow-cljs.github.io/docs/UsersGuide.html#dev-http seems to imply that it is, but when I try

:dev-http {8081 "resources/public"
            8444 {:root "resources/public"
                  :ssl true}}