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]}

and that's it

@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

https://github.com/plexus/synaethesia/blob/master/src/syna/esth/proc.cljs

https://github.com/plexus/synaethesia/blob/master/src/syna/esth/strm.cljs

for example

(| (<file "input.txt")
   (cmd! ["grep" "foo"])
   (cmd! ["tac"])
   (>file "output.txt"))

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)

neat 🙂 I like it

@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