Closed juanpr2 closed 8 years ago
I'm not all that familiar with the nrepl features of figwheel and what it is supposed to give me of benefits as opposed to using the lighttable with cljs browser eval. Once we do figure it out, we should probably add a section about Light Table on the figwheel wiki :-)
Here's what I did get something up and running though:
lein repl
(use 'figwheel-sidecar.repl-api)
(start-figwheel!)
(ns user.whatever (:require [hello-om.start-ui :as ui]))
If I edit cljs files all workes as expected, the compiled js is loaded into the browser and so is then available for cljs evals in LT.
I'm still confused about piggieback, weasels and whatnot. But I'm not sure why you would ever need it from Light Table as it ships with it's own middleware that handles eval in either LT internally (very limited clojurescript version support), internal browser or external browser.
hope this helps.
Here's a screenshot of LT working with figwheel. I'll have a wiki page up soon:
Made https://github.com/bhauman/lein-figwheel/wiki/Running-figwheel-with-LightTable. Closing for now but can reopen if it doesn't work and you can give me steps like ones I listed on the wiki page
Curious if there's any way to make LT connect to an external figwheel REPL (not an internal figwheel browser)?
My goal is to onboard a couple people onto a ClojureScript project without throwing Clojure, Emacs/Vim, and Paredit at them all at the same time, but I'd still like them to have an in-editor REPL. For some reason when using the internal Figwheel REPL a couple Chrome APIs aren't working, and I can't see the dev console.
Unfortunately, I don't have enough exposure on the topic to be of use but perhaps @rundis or @cldwalker know something?
LightTable gives an error when trying to connect to Figwheel's repl.
Following the steps:
lein figwheel
The blocks spin with the message Connecting.., but nothing happens.
I'm using LightTable version 0.8.0-alpha, Binary version 0.31.1 on a Mac with OS X 10.10.5.
This is my project.clj
Any help is appreciated, thanks.