I'm getting shadow-cljs stale client - you're not using the latest compilation output for some reason. I deleted my target and my out files and rebuilt using (shadow/watch :app) but I still get this prompt. How do I fix this?

Also, in the repl I get

No application has connected to the REPL server. Make sure your JS environment has loaded your compiled ClojureScript code.

@pshar10 you fix that by loading the correct files. seems like you maybe cleared the wrong directory or wrong server or so.

@thheller found 1 reason to use ^:const , you can't use a def in a case

?

(let [test 4] (case test constants/command-state-request-transaction true false))

evals to false

constants/command-state-request-transaction is def to 4

thats a bug in CLJS then

https://blog.fikesfarm.com/posts/2015-06-15-clojurescript-case-constants.html

try it in CLJ

user=> (def ^:const y 1)
#'user/y
user=> (case 1 y true false)
false
user=> (case 'y y true false)
true

so you mean that the fact that it works in cljs with a const is a bug?

no clue. I never use ^:const for anything. Maybe this is intentional. Maybe it actually works in CLJ and I'm just doing something wrong. the clojure docs clearly state that the test contants are not evaluated

http://clojuredocs.org/clojure.core/case

so looking up the var and seeing it was a const would imply some evaluation

IMHO that would be a bug but IMHO the entire :const impl in CLJS is a bug

I tried to put :source-map false :source-map-include-sources-content :false in compiler options for :dev build but I still see source maps files in the output dir, does it mean it didn't work? (I cleaned all dir before recompiling)

mhm I see this is known https://github.com/thheller/shadow-cljs/issues/328

@thheller would it be possible to allow disabling source-maps in dev? main reason is that they are mostly useless in react-native and result in huge bundles

@yenda how do they result in huge bundles? they aren't inlined?

if you want to have a look that's our index.js

btw do you think it would be possible for shadow to write index.js in a temp file and replace it only once it is done writing? to avoid the metro bundler bug

hmm it seems I forgot that react-native actually inlines the source maps

can't remember why though

I can certainly allow to disable that

ah I think that was the only way to get the source maps to work at all when running the debug-in-chrome thingy

and how does the rewriting of the index.js works? would it be possible to do it in a temp file first ?

I don't really like working around bugs in other tools but sure I can add that

uhm doesn't :compiler-options {:source-map false} not already turn off the source maps?

I tried but I could still see .map files and the index.js looked like it was same size

hmm yeah indeed

Why doesn't macro expand work in the cljs repl?

I define a macro in a clj file myapp.macros

and then require it in myapp.macros cljs file

and then use the macro in a third file

when I macro expand in the clj repl, the macroexpansion works:

(macroexpand '(db-event :foo [foo bar] [:foo foo :bar bar]))

(do
 :foo
 (clojure.core/fn
  [db__49764__auto__ [foo bar]]
  (clojure.core/apply
   clojure.core/assoc
   db__49764__auto__
   [:foo foo :bar bar])))

(macroexpand '(db-event :foo [foo bar] (assoc db :foo foo :bar bar)))
=> (db-event :foo [foo bar] (assoc db :foo foo :bar bar))

@pshar10 just a guess but maybe you didn't follow the instructions I sent you before again? https://code.thheller.com/blog/shadow-cljs/2019/10/12/clojurescript-macros.html

if you don't do all of those steps then macros will not work as you expect

and you cannot define a macro from a REPL unfortunately currently

well you can if its a CLJ REPL but that doesn't get you around the other limitations

wrote a new post https://code.thheller.com/blog/shadow-cljs/2020/05/08/how-about-webpack-now.html for people asking about how :bundle affects shadow-cljs