Clojurians Log v2

FWIW the code in y.clj is basically

(def route-data
  (set (map (fn [] ...) z/all-routes)))

(defmacro make-href
  "Variant of make-href* that tries to validate the route at compile time."
  [route]
  (if-let [kw (if (keyword? route)
                route
                (as-> (:route route) $ (when (keyword? $) $)))]
    (if (contains? route-ks kw)
      `(make-href* ~route)
      (-> (str "Failed to build href for route: " (fmt/ppr-inline route)
               "\nDefined routes: " (fmt/ppr-inline route-ks))
          (ex-info {})
          throw))
    `(make-href* ~route)))

CLJ reloading is limited, so I'd recommend something like clj-reload to get something that is more optimized for CLJ

or you can always just edit the file and reload it from the REPL directly

but it still has limits in how far shadow-cljs follows CLJ dependency graphs

cool, thanks

I didn't know about clj-reload; here I am still using tools.namespace like a caveman

that error usually means that there is a "competing" shadow-cljs instance. could be that its running twice? maybe in a second terminal or so?

or it could be an old file you are actually loading because of some old references. did you maybe change the :output-dir or :modules config recently?

make sure your html is loading the files this is actually generating, so the cljs-out/base.js and cljs-out/main.js files

dunno why there is a :portfolio module in the :app build when there is an extra :portfolio separate build? seems like that isn't needed?

also why are you downgrading to :output-feature-set :es6? you really target 2015 browsers?

:infer-externs :auto is the default and does not need to be set

seems like this config for :app would suffice

{:output-dir "projects/frontend-web/resources/public/cljs-out"
 :asset-path "/cljs-out"
 :target :browser
 :modules {:main {:init-fn com.app.example-web.dev/launch}}
 :devtools {:after-load app.main/reload!}}

Thanks for these suggestions, I know I do not have another instance of shadow running. So I will try the other suggestions, also if you just watch without connecting any idea I would expect it would not be stale, not at a machine to test but will let you know, if nothing else may help others or myself when searching :)

what you need to verify is that the .js files you are loading are produced by the actual shadow-cljs

so best is to shut down shadow-cljs, delete all generated files and start, verifying that the files you deleted actually get generated and that there are no duplicates in other folders

could also just be browser cache is thats not setup properly, but :dev-http usually does that by default

if a service-worker is involved that might different

Awesome think I understand now, its where I have changed things over time I think I started of having portfolio as a separate build, then realized I could use the modules to code split to make the app and portfolio run at the same time by having index.html and portfolio.html and loading the relevant js files in each. I have not worked on the project for a while and come back to it and forgot that, you are correct though removing the cljs-out folder cleared up everything then I could see that portfolio.js was not created but main.js was which is whats specified in the :portfolio build where as :app generates base.js main.js and portfolio.js. Thanks so much @thheller I will make the other changes as well, most likely it me copying and pasting on some of the settings from known working configs.

I recommend leaving portfolio stuff out of the main build. it'll just get you in trouble for production builds.

npx shadow-cljs watch app portfolio can just build 2 builds in parallel, so multiple builds is no issue

that's awesome it had never occurred to me I could chain them