I always have problems to make the repl (and cider) work properly:

(defproject [...]
[...]
:plugins [[lein-environ "1.0.2"]
[lein-cljsbuild "1.1.5"]
[lein-shell "0.4.0"]
[cider/cider-nrepl "0.16.0"]
[lein-asset-minifier "0.2.7" :exclusions [org.clojure/clojure]]]
[...]
:figwheel {:http-server-root "public"
:server-port 3449
:nrepl-port 7002
:nrepl-middleware ["cemerick.piggieback/wrap-cljs-repl"]
:css-dirs ["resources/public/css"]
:ring-handler ui-app.handler/app}
[...]

$ lein repl  
[...]
#error {
 :cause Unable to resolve symbol: wrap-file-info in this context
 :via
 [{:type clojure.lang.Compiler$CompilerException
   :message java.lang.RuntimeException: Unable to resolve symbol: wrap-file-info in this context, compiling:(ui_app/repl.clj:19:7)
   :at [clojure.lang.Compiler analyze Compiler.java 6792]}
  {:type java.lang.RuntimeException
   :message Unable to resolve symbol: wrap-file-info in this context
   :at [clojure.lang.Util runtimeException Util.java 221]}]
 :trace
 [[clojure.lang.Util runtimeException Util.java 221]
  [clojure.lang.Compiler resolveIn Compiler.java 7299]
 

(I'm actually trying to make cider run, but if the repl doesn't work properly, I suppose I won't get cider-nrepl working properly either)

@kurt-o-sys this isn’t a leiningen error - you are using something called wrap-file-info in the file ui_app/repl.clj that doesn’t exist (or you are using some macro that does so)

oh, ok... well, I'm just trying to get cider nrepl working in spacemacs, so... where's the error, so I can post this on the right channel...

you can start a repl without loading your namespace by changing your init-ns to user, or running lein run -m clojure.main

@kurt-o-sys the error is something in your code, if the code uses wrap-file-info. If it’s a macro using wrap-file-info and not your code directly, it’s a bug in whatever defined that macro

it's just a lein template for clojurescript... not 'my' code.

which clojurescript template?

https://github.com/Day8/re-frame-template

if you haven’t modified the code, then it’s a re-frame bug, and you can check the #re-frame channel

ok, thx.