This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # arachne (2)
- # architecture (23)
- # bangalore-clj (5)
- # beginners (35)
- # boot (79)
- # cider (6)
- # cljs-dev (34)
- # cljsrn (9)
- # clojure (164)
- # clojure-argentina (2)
- # clojure-austin (4)
- # clojure-italy (7)
- # clojure-russia (40)
- # clojure-serbia (1)
- # clojure-spec (76)
- # clojure-uk (36)
- # clojurescript (47)
- # cursive (14)
- # datascript (2)
- # datomic (8)
- # dirac (19)
- # emacs (29)
- # heroku (7)
- # hoplon (35)
- # jobs-rus (1)
- # juxt (2)
- # leiningen (1)
- # lumo (23)
- # mount (4)
- # off-topic (22)
- # om (16)
- # onyx (19)
- # parinfer (10)
- # pedestal (47)
- # proton (5)
- # re-frame (88)
- # rum (1)
- # spacemacs (33)
- # sql (29)
- # uncomplicate (1)
- # unrepl (131)
- # untangled (5)
- # yada (12)
hey guys, I've just ran into this really strange problem where I'm building in
:optimizations :none and one of my 3rd party modules isn't loaded on Firefox (linux, 51). The module is compiled, it's declared in
cljs_deps.js and it works perfectly in chromium.... Looking at Firefox's network tab, this module was never even requested by the browser... Any ideas? I've been looking into this problem for hours now.
ok, I was just being stupid... it was a google analytics module and my browser plugin blocked it (facepalm) which in turn crashed the whole app because of undefined stuff.
@superstructor sorry, had to leave with family business, I am running the same CLJS version. I did a lein ancient upgrade on the project, the library that initiates the failure is the reagent one. I am thinking it is actually a react change that was done...
@credmp it may be relevant to know that I exclude react/react-dom from reagent dep as it is included for us in Material-UI 0.17.0 (via cljs-react-material-ui) which we also use.
mmm I will give that a try, perhaps there is something in de react changes that introduces it
The setup I have is quite straightforward (standard), so probably more people will run into it as they update
speaking of cljs and macros, what's the difference between :require-macros and :refer-macros?
I just now realize that what I’m trying to do might be possible without a macro in the first place
(:require [dommy.core :refer-macros [sel1]]) vs (:require-macros [cljs.core.async.macros :refer [go]])
kind of weird that it’s not just
:refer like in clojure.
[somelib :refer [macro]
[somelib #?(clj :refer :cljs :refer-macros) [macro]]
@hkjels see Implicit macro loading at https://github.com/clojure/clojurescript/wiki/Differences-from-Clojure#namespaces
I'm no designer, I only want components to build app-ui, not impressive html5 "experiences".
@not-raspberry I'm using getmdl from google right now and I really like it. Works and looks great on mobile and desktop.
CodeMirror works as well, you will be writing a bunch of native JS interop no matter what
Has anyone ever encountered a RangeError maximum call stack exceeded involving core.async and figwheel?
@superstructor I tracked down the problem. In https://github.com/reagent-project/reagent/issues/275 there is a mention of the rename of
React.DOM. So reagent upgraded to 15.4, in
lein deps :tree I noticed that
devcartswas pulling in an older version. I added an
:exclusions for it and the problem was fixed.
I’ve checked for circular dependencies, have found none. I even rollback to a working commit and I’m still getting the error
@mruzekw: What versions of figwheel and core.async are you using? Every time I’ve run into weird problems with figwheel some combination of versions, lein clean or computer restart have fixed them for me - but that’s on Windows so restart is kind of assumed 🙂
Compare it to what comes with
lein new figwheel, it includes core.async specifically. Might be the problem if it’s missing and needs to be there.
Well, did lein clean, restarted both server and figwheel, reapplied stashed changes, and all is well again