This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-23
Channels
- # beginners (27)
- # boot (8)
- # cider (17)
- # cljs-dev (8)
- # cljsrn (5)
- # clojure (56)
- # clojure-dev (34)
- # clojure-gamedev (4)
- # clojure-italy (32)
- # clojure-nl (22)
- # clojure-poland (3)
- # clojure-russia (17)
- # clojure-spec (31)
- # clojure-uk (48)
- # clojurescript (47)
- # core-async (41)
- # cursive (13)
- # datomic (22)
- # emacs (9)
- # figwheel (7)
- # fulcro (18)
- # graphql (3)
- # hoplon (15)
- # jobs-discuss (38)
- # keechma (1)
- # luminus (10)
- # off-topic (42)
- # onyx (8)
- # overtone (3)
- # protorepl (5)
- # re-frame (42)
- # reagent (6)
- # reitit (3)
- # schema (4)
- # shadow-cljs (39)
- # slack-help (5)
- # spacemacs (8)
- # specter (1)
- # tools-deps (36)
- # uncomplicate (9)
- # vim (34)
$ lein figwheel
Figwheel: Cleaning because dependencies changed
Figwheel: Cutting some fruit, just a sec ...
Figwheel: Validating the configuration found in project.clj
java.lang.NullPointerException
at clojure.zip$node.invokeStatic(zip.clj:67)
at clojure.zip$node.invoke(zip.clj:64)
The stack trace is, as they are, long, but passes through figwheel-sidecar
among other places.
Seeing it with Java 1.10 / Clojure 1.8 / fighwheel 0.5.10; still working on checking other versions, etc.
Ahh. Okay: I've nested my cljsbuild
spec inside a profile. If I move the whole thing outside the profile, I get a very polite error message asserting a key is missing. So. Just an odd edge-case with the error reporting + missing a key.
I'm working on an existing project in Angular that uses ngrx, which is essentially just a Redux implementation (unfortunately, I don't have the pleasure of using ClojureScript on this project). The ngrx team doesn't see the point of hot module replacement, but a couple people have built their own implementations. One of them just serializes everything and sticks it in local storage, and then re-hydrates it when the new code is loaded. Off the top of your heads, is there anything inherently wrong with that approach?