hi. shadow-cljs has been reporting this on my build:

------ WARNING #1 --------------------------------------------------------------
 File: bidi/bidi.cljc:29:12
--------------------------------------------------------------------------------
  26 | actually a valid UUID (this is handled by the route matching logic)."
  27 |   [s]
  28 |   #?(:clj (java.util.UUID/fromString s)
  29 |      :cljs (cljs.core.UUID. s)))
------------------^-------------------------------------------------------------
 Wrong number of args (1) passed to cljs.core.UUID
--------------------------------------------------------------------------------
  30 | 
  31 | ;; When forming paths, parameters are encoded into the URI according to
  32 | ;; the parameter value type.
  33 | 
--------------------------------------------------------------------------------

probably yes

they are supposed to use (cljs.core/uuid s)

or just (uuid s)

ok, I'll open an issue on their repo.

nevermind, there is already an issue on this: https://github.com/juxt/bidi/issues/189

Hi thheller, FYI I've got asset fingerprinting working in a configure build hook similar to how we outlined it last week. Deploying today. If it all works then I'll run the implementation past you.

I think there's still quite a bit of work required before it's ready for a PR into shadow-cljs.

shadow-cljs just started reporting this on a project I hadn't touched for a few weeks:

@mattly shadow 2.7.x requires CLJS 1.10.439

so need to bump that when using deps.edn

huh thanks

I don't remember upgrading anything

thanks

you probably have a version range in your package.json for shadow-cljs

"shadow-cljs":"^2.6.12" or whatever

yeah indeed

that automatically upgrades

can just set a fixed version (which I recommend doing)

to avoid issues such as this 😉

yeah that's typically what I do

no idea why version ranges are still the default in node world 😞

perhaps because they think anything older than a day is obsolete

hehe