This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-10
Channels
- # admin-announcements (1)
- # alda (1)
- # bangalore-clj (1)
- # beginners (94)
- # boot (139)
- # braveandtrue (1)
- # cider (19)
- # cljs-dev (21)
- # cljsjs (8)
- # cljsrn (79)
- # clojure (124)
- # clojure-austin (1)
- # clojure-belgium (1)
- # clojure-berlin (3)
- # clojure-hamburg (3)
- # clojure-quebec (1)
- # clojure-russia (77)
- # clojure-spec (5)
- # clojure-uk (18)
- # clojurescript (39)
- # conf-proposals (21)
- # core-async (5)
- # cursive (8)
- # datomic (40)
- # defnpodcast (1)
- # devcards (14)
- # dirac (5)
- # editors (1)
- # emacs (4)
- # jobs (1)
- # liberator (4)
- # onyx (29)
- # perun (15)
- # proton (15)
- # protorepl (9)
- # re-frame (47)
- # reagent (38)
- # ring (1)
- # rum (7)
- # specter (23)
- # untangled (8)
- # yada (55)
@porglezomp: just look this examples, in this example i used production mode, also you can see results on development mode https://github.com/manishkumarmdb/cljsjs-interop-workshop
Hi! My cljsbuild has started hanging (i.e. not exiting) after successful compilation (and after applying optimization levels). Anyone ever stumbled on this?
with the following config:
:cljsbuild {:builds
[{:id "min"
:source-paths ["src"]
:compiler {:output-to "resources/public/js/compiled/compiled.js"
:main mynamespace.core
:optimizations :simple
:verbose true
:pretty-print false}}]}
I refactored some namespaces and yesterday wasn't working because the source-paths were wrong (so it had nothing to compile and "failed" silently). Now I honestly don't know what to do, because the config looks fine.
@tap I finally hunted it down with git bisect. It was a call to (flake/init!)
in the clj backend namespace that made the cljs compiler hang, even if it was totally another source path (no overlapping). Is this a cljs compiler bug?
@nilrecurring: i think you'r using in development mode, so you should update :optimizations :simple to :none , because :none is the recommended setting for development.
@manishkumarmdb: if you read up we're talking about the production build, which I do with the "min" profile, and optimizations advanced (simple in the snipped I pasted because I was invastigating about where the issue was exactly)
But the issue here is that the cljs compiler was looking into the clojure source path and hanging on that direct call to the flake init ^
@borkdude: I haven’t personally, but pebble is quite memory constrained I think, 64kb only? they have a custom javascript engine and I don’t think cljs persistent data structures would play well in such memory constrained environment even with DCE
@sivakumargsk: (clojure.string/join " " (re-seq #"[A-Z][a-z]+|[0-9]+" "SivaKumar25689”))
works for your example
Just getting started with spec and I’m getting the following error. Looks to me like cljs.spec/coll-of
should indeed take a single arg.
Wrong number of args (1) passed to: spec/coll-of
89 (s/def ::orig-pdf-blob-id (s/nilable string?))
90
91 (s/def ::pages (s/coll-of ::page))
^--- Wrong number of args (1) passed to: spec/coll-of
92 (s/def ::recipients (s/coll-of ::recipient))
93 (s/def ::fields (s/coll-of ::field))
later when we have a release at parity with Clojure we can take feedback about problems
@anmonteiro: very cool, thanks for the blog - I didn't know clojurescript supported use
though