This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-21
Channels
- # aatree (88)
- # admin-announcements (14)
- # alda (26)
- # announcements (4)
- # avi (6)
- # aws (7)
- # beginners (80)
- # boot (268)
- # braid-chat (58)
- # cider (4)
- # clara (54)
- # cljs-dev (16)
- # cljsrn (27)
- # clojars (13)
- # clojure (123)
- # clojure-chicago (2)
- # clojure-czech (8)
- # clojure-france (5)
- # clojure-hamburg (2)
- # clojure-miami (6)
- # clojure-nl (5)
- # clojure-russia (285)
- # clojure-spain (2)
- # clojurebridge (3)
- # clojurescript (137)
- # code-reviews (14)
- # community-development (6)
- # core-async (8)
- # core-matrix (10)
- # cursive (2)
- # datascript (1)
- # datomic (24)
- # dirac (2)
- # emacs (5)
- # hoplon (4)
- # incanter (6)
- # jobs (7)
- # ldnclj (42)
- # ldnproclodo (2)
- # leiningen (1)
- # mount (60)
- # off-topic (15)
- # om (134)
- # onyx (65)
- # perun (4)
- # portland-or (2)
- # proton (15)
- # random (1)
- # re-frame (24)
- # reagent (7)
- # testing (4)
- # yada (9)
With [email protected] source maps should be available when you are debugging in chrome.
…by making a one small line change to the RN packager source inside your node_modules folder
@drapanjanas: Did you thought about contributing that change to RN back?
@mfikes: Thank you once again for your Planck! Gonna rewrite all ugly bash mess for https://github.com/artemyarulin/clojure-clojurescript-buck to planck
Cool! Yeah… I’ve been actually using it to deploy my blog, to print out barcodes, etc., stuff that used to be in Bash
@artemyarulin I thougt about it and would be glad to. But I have no idea how would I make it fit RN packager... Its a hack which does not make sense for JS.
hm, I mean I’ve seen changes that were made only because of Scala.js so you could try at least. Introduce an option/config or something like that
Hmm, In that case, maybe worth trying
@mfikes: I’m parsing Clojure files, is this a right approach or I’m using Planck in a wrong way? LIke:
(ns cljs.user
(:require [planck.repl :as repl]
[planck.core :as core]))
(nth (first (repl/repl-read-string (core/slurp "buck-out/gen/clojure/yieldm/project/project.yieldm/project.clj"))) 4)
# [[aleph "0.4.1-beta2"] [org.clojure/clojure "1.8.0"] [org.clojure/tools.namespace "0.3.0-alpha3"]]
not the ugly part about actual parsing, but the thing that I require repl and call repl-read-string from it?
@artemyarulin: Normally you wouldn’t require the planck.repl
namespace. (The definition of repl-read-string
could change.) But, you should be able to use the reader…
Yeah, I was looking for the way how can I get a reader but didn’t find it
cljs.user=> (require 'cljs.tools.reader)
nil
cljs.user=> (cljs.tools.reader/read-string "[1 2]")
[1 2]
@artemyarulin: The equivalent should work in code, as opposed to in a REPL, as illustrated above.
Oh, I feel ashamed now
@mfikes: Thank you!
No problem. You can be guaranteed that Planck will ship with cljs.tools.reader
as a bundled dep.
Nice, this makes so many things easier for me. Really happy that finally found a time to try it
Gonna use it for scripting for sure. Thanks again for this awesome project!
@mfikes: Last question - is there any Windows/Linux support for Planck? And if there are any plans?
Found the discussion here already https://github.com/mfikes/planck/issues/1
No, but half plans. I've built JavaScriptCore on Linux and have an idea of converting the Planck Objective-C to C.
Yeah, understand that
Oh found a solution - I’m gonna use Planck if it’s available on a system and if not - I’ll fallback to clojure which would affect startup time but at least I would get my CI working