gistfile1.clj

{:optimizations :none
 :output-dir "samples/hello/out"
 :output-to "samples/hello/out/hello.js"
 :source-map true}

Currently print-mapped-stacktrace takes a path from the root of the project.

  (print-mapped-stacktrace
    [{:file "samples/hello/out/hello/core.js" <-- path from project root
      :function "first"
      :line 2
      :column 1}])
  )

Some clients are getting there code from a server and thus don't have project root paths. 

In fact the client side paths can be arbitrary in a way that is difficult and non trivial 
for repl server code like IJavaScriptEnv's to deduce the correct project root path from.

For instance if a browser (figwheel) client is getting its code from localhost/arbtirary/path/to/example/core.js
but :output-dir is "out", how is the IJavaScriptEnv supposed to reliably calculate the 
path from project root.

Because all clients can easily calculate the output-dir relative path with js/goog.basePath:
output-dir_relative_path ~=~ path - ( js/goog.basePath - #"goog/$")

I think it may be more general to take an output-dir relative path from base like so: 

(print-mapped-stacktrace
    [{:file "hello/core.js" <-- path from output dir
      :function "first"
      :line 2
      :column 1}]))

I'm solving this problem in figwheel by calculating the output-dir_relative_path client side
then having the IjavaScriptEnv prepend the :output-dir