You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More of a question than an issue, because I can't see where this happening after cursory inspection. I've got a dependency (Timbre) which conditionally writes to stdout at compile time. While that may not be a fantastic idea itself, when doo compiles my build the console output is redirected to the source file.
// Compiled by ClojureScript 1.8.51 {:target :nodejs} Compile-time(elision)Timbrelevel: :warngoog.provide('taoensso.timbre');
The middle line being the problem. Thoughts?
Compiling via lein doo node test-none once, project file is here
The text was updated successfully, but these errors were encountered:
Hey! I didn't try using the compiler directly, but no, it doesn't happen with cljsbuild. w/ cljsbuild I see the compiler's console output and the print statement, which w/ doo is I guess is swallowed by whatever leiningen.core.eval is doing with subprocess output - which I can't really follow.
This is a doo issue then. It is important to redirect the standard output of some process to get the error reporting, but the compiler should fall into that. I'll look into it and see what is the best way to solve it.
More of a question than an issue, because I can't see where this happening after cursory inspection. I've got a dependency (Timbre) which conditionally writes to stdout at compile time. While that may not be a fantastic idea itself, when doo compiles my build the console output is redirected to the source file.
The middle line being the problem. Thoughts?
Compiling via
lein doo node test-none once
, project file is hereThe text was updated successfully, but these errors were encountered: