Can someone sorta explain how the cljs browser repl works with regards to eval'd values and re-compilation? It's kind of magic how I can declare an atom, and then reset! the value when the code path is executed by me in the browser and deref that value in the repl to mess around with it. Is there a way to persist that value in the repl so that it survives a re-compilation?

oh I guess I could shove it into local-storage

also is it possible to declare 'global' functions that are available at the repl no matter which namespace is currently selected?

this is all inside the cljs-repl started via (shadow/nrepl-select :app)

you can make a value survive recompilation by using defonce instead of def. that’s what you’ll want to with your application state

i’m not sure what you mean by >then reset! the value when the code path is executed by me in the browser and deref that value in the repl to mess around with it.

@haywood ^

ah awesome

I mean:

doing stuff like that, where I want to mess around with a value so I'll reset it in an atom. 'exercise' the code in the browser, come back and the atom will have the value

it's pretty magic, and awesome

lines 3 and 5 are afterwards when I'm messing around

oh man, defonce is a game changer thanks

maybe the piece you are missing is that when you drop into the cljs repl (by calling (shadow/nrepl-select :app) you are actually running code on the browser

whatever code your run in the cljs repl is just like running javascript in the browser console, except that it gets compiled to js first

yea the fact that I can write arbitrary code, eval it in the repl, and it gets compiled on the fly down to javascript and eval'd in the correct place is pretty wild

you're right

is there a way to declare values in the repl that are "above" or global to all namespaces?

that’s why the cljs repl is often totally effed up and hard to get going. you have a menage a trois of the browser, your editor / tty, and cljs compiler (which is running in java)

i don’t think so. people often ask for it but i haven’t seen an answer

cool

yea it's been working great for me, especially paired with debux

so I was able to import debux and declare a 'global' dbg atom in cljs.user. and I can refer to those globally by fully qualifying the namespace 🙂

that basically satisfies my request for global stuff