This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-15
Channels
- # beginners (15)
- # boot (4)
- # cider (1)
- # cljsrn (16)
- # clojars (1)
- # clojure (92)
- # clojure-india (3)
- # clojure-russia (27)
- # clojure-spec (9)
- # clojure-uk (5)
- # clojurescript (73)
- # cursive (28)
- # datascript (10)
- # emacs (1)
- # events (5)
- # hoplon (1)
- # instaparse (7)
- # juxt (2)
- # klipse (13)
- # lumo (17)
- # off-topic (166)
- # onyx (4)
- # protorepl (5)
- # re-frame (5)
- # reagent (13)
- # rum (26)
- # untangled (17)
- # yada (3)
Is there any way to get a line number or stack trace on errors? I'm seeing things like this
> #error {:message ERROR in file syna/esth/esia.cljs, :data {:tag :cljs/analysis-error}, :cause #object[TypeError TypeError: path must be a string or Buffer]}
@plexus, I've had that problem too
strangely, sometimes you get stacktraces, sometimes you don't
@plexus, I think it's tracked here: https://github.com/anmonteiro/lumo/issues/36
@pesterhazy thanks!
maybe folks are interested in this stuff, I've been writing some wrapper and utility functions around node's process and stream stuff
so far strictly home brewed for my own purposes, but might give folks ideas for a repl utility library for lumo
that pipe function is built on a Pipe protocol
(defprotocol Pipe
(-source [this])
(-sink [this]))
which means you can use a bunch of different things in there, different types of node streams, buffers, the result of cmd!
(which is a custom record)
@plexus Cool stuff! If you haven't already seen these, you might be interested in https://github.com/abiocljs/abio and https://github.com/pkpkpk/cljs-node-io