This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-09
Channels
- # adventofcode (93)
- # announcements (11)
- # babashka (7)
- # babashka-sci-dev (17)
- # beginners (73)
- # biff (7)
- # calva (3)
- # cider (1)
- # clj-kondo (160)
- # clj-together (12)
- # clojure (44)
- # clojure-art (2)
- # clojure-europe (12)
- # clojure-losangeles (1)
- # clojure-nl (3)
- # clojure-norway (22)
- # clojure-uk (2)
- # clojurescript (8)
- # clr (1)
- # cursive (6)
- # data-science (1)
- # datomic (1)
- # emacs (6)
- # events (1)
- # exercism (1)
- # fulcro (6)
- # graphql (2)
- # introduce-yourself (1)
- # lsp (18)
- # nrepl (7)
- # off-topic (45)
- # polylith (25)
- # portal (25)
- # practicalli (3)
- # re-frame (14)
- # reagent (28)
- # reitit (2)
- # releases (2)
- # shadow-cljs (73)
- # sql (11)
- # tools-deps (12)
- # transit (4)
- # xtdb (4)
hey all - is there some way to get my reagent project to NOT use the minified production version of react?
I am seeing some errors that I am having a lot of trouble debugging
coming from react…
but this only happens on the first page load after I rebuild the javascript, EVEN THOUGH the browser is not caching main.js
??
with source maps:
depending on what build tool you're using, you can provide different files for your JS dependencies
but only on the first load, once I serve the file with http-server
. it doesn’t seem to happen on first load at
, where I’ve deployed the file, either
so it’s a transient local thing? but I don’t get how that could be happening with no caching of the file
if you reload does it persist?
yeah, I fixed that, that was a separate issue
just haven’t deployed yet
I also don’t see it on safari, just on brave
interesting… so if I DON’T regenerate the file, but simply restart the http-server, then I get that failure again
oh, I think I’ve pinned down what’s going on
I can pretty reliably trigger the error if i open the page without devtools opened in Chrome
it is happening when I try and interact with this defonce
form:
all of this code is actually running inside of an sci
environment, so something suspicious is happening here
okay, I fixed it by renaming that atom. this feels like something with sci
thanks for staring with me!
@lilactown I figured it out… I was using a useEffect
hook and had a code path that returned nil
from my mount
function, instead of an unmount function.
looks like in react 18, with advanced compilation, that triggered a bug