nREPL

If you would like to send every REPL eval to Portal, you can use the portal.nrepl/wrap-portal nrepl middleware.

The main advantage of using this middleware is that it can capture additional information about your REPL interaction, such as:

• Source and file info
• Runtime type (very handy for cljc files)
• Timings
• Test assertion output
• Eval exceptions
• Stdio

tools.deps

If you are starting nrepl from tools.deps, you can try the following:

;; deps.edn
{:aliases
 {:nrepl
  {:extra-deps
   {cider/cider-nrepl {:mvn/version "0.28.5"}
    djblue/portal     {:mvn/version "0.33.0"}}
   :main-opts ["-m" "nrepl.cmdline"
               "--middleware"
               "[cider.nrepl/cider-middleware,portal.nrepl/wrap-portal]"]}}}

shadow-cljs

If you are using shadow-cljs, you can add the middleware via the shadow-cljs.edn file:

;; shadow-cljs.edn
{:nrepl {:middleware [portal.nrepl/wrap-portal]}}

leiningen

If you are starting nrepl via lein repl, you can try the following:

(defproject app "0.1.0-SNAPSHOT"
  :dependencies [[djblue/portal "0.33.0"]]
  :repl-options {:nrepl-middleware [portal.nrepl/wrap-portal]})

Or via a dev profile:

(defproject app "0.1.0-SNAPSHOT"
  :profiles
  {:dev {:source-paths ["dev"]
         :dependencies [[djblue/portal "0.33.0"]]
         :repl-options
         {:nrepl-middleware [portal.nrepl/wrap-portal]}}})

Customization

If you would like to process eval results, you can do so with a custom tap handler, such as the following:

(require '[portal.api :as p])

(defn submit [value]
  (if (-> value meta :portal.nrepl/eval)
    (let [{:keys [stdio report result]} value]
      (when stdio (p/submit stdio))
      (when report (p/submit report))
      (p/submit result))
    (p/submit value)))

(add-tap submit)