aaaand as so often, right after posting a question, I stumple over a solution. Just adding :dependencies [cljsjs/nodejs-externs "1.0.4-1"] is one solution. Sorry! And thanks for just being there. This is an awesome community.

I have personally never been a fan of most routing framework approaches; IMO they make things way too complicated for what they provide; If you want “routing”, it doesn’t take much to set it up yourself based on, say, anchor hash value https://www.w3schools.com/jsref/prop_anchor_hash.asp ; now if you want to parse parameters, etc, etc you might want to consider a library

Modern browsers can help avoid using hash fragments and just use regular URL path for that. This is the API: https://developer.mozilla.org/en-US/docs/Web/API/History_API

For how browser routing works at a low level I highly recommend JS talks by any of the people who wrote the big JS routing libraries. They will explain the problem space context nicely. Then come back to cljs land with that knowledge and take a look at reitit and secretary to see how they handle the problem.

Note that you don't need secretary to use reitit. I highlight those as libraries which are solving similar problem in different ways

@U6GNVEWQG Could you please recommend some library like that? I am new in this...

react-router, vue-router etc

As in, the :opacity won’t magically turn into an ‘oX’ or something 😄

(I think it’s safe but I thought I saw a discussion at some point about certain gotchas around interop, I could be mistaken)

it can be renamed if there are not externs

but there are externs for opacity so its safe

If it's some name that doesn't have an extern, how to prevent it from being mangled, without having to write explicit externs? Is there a way to do it with ^js?

not actually sure

Hmm so if it’s a custom name, unlike :opacity, it’s not considered safe? So something like https://github.com/raspasov/alexandria-clj/blob/main/src/ss/react/core.cljs#L63 would not be safe? :_cljs

At the same time, I’ve been compiling this for a long time with :advanced and not run into problems… I guess it might be a problem if you try to access it like (.-_cljs my-js-obj) ?

Aha! And because I have this… https://github.com/raspasov/alexandria-clj/blob/main/src/ss/react/core.cljs#L95 It’s safe…

(defn props-class “Get props for class components” [^js/Object this] (.. this -props -_cljs))

Because of the hinting.

Yeah, maybe something like

(defn ^:export -dummy [^js x]
  (.-_cljs x))

#re-frame would be a more suitable place.

Just a stylistic thing. Brackets are generally more often recommended.

Like with nrepl or just a plain cljs repl?

just a plain CLJS repl is fine

from my terminal

clj -Sdeps '{:deps {org.clojure/clojurescript {:mvn/version "1.10.844"}}}' \
    -m cljs.main -re node

😐 that is incredibly close to what I've been attempting

https://clojurians.slack.com/archives/C6QH853H8/p1618250174465300

yours works tho 😄

tyvm

Similar:

clj -Sdeps '{:deps {org.clojure/clojurescript {:mvn/version "RELEASE"}}}' -M -m cljs.repl.node

That's weird, they look identical lol

the :deps map is missing 😉

omfg

Well there it is 👌

clj -Sdeps '{:deps {thheller/shadow-cljs$aot {:mvn/version "RELEASE"}}}' -M -m shadow.cljs.devtools.cli node-repl 😉

Wait... is $ how you specify a classifier?

will break horribly though since npm packages are missing 😉

lol

yes

I'm trying to report a CLJS bug so I want to keep it minimal

Used to work with Java directly, but learned about Maven classifiers via a question about CLJS REPL. :D

https://gist.github.com/raspasov/978ccb338e4b8c56513c10d3523877c7