#figwheel — Public Fediverse posts

The language #Clojure and #ClojureScript languages are so stable, with breaking changes being frowned upon in the culture. But breaking in the (frankly, awesome!) tooling has been my difficulty as I maintain a dozen projects of varying ages. It is a real problem. #cider #nrepl #figwheel #piggyback

The language #Clojure and #ClojureScript languages are so stable, with breaking changes being frowned upon in the culture. But breaking in the (frankly, awesome!) tooling has been my difficulty as I maintain a dozen projects of varying ages. It is a real problem. #cider #nrepl #figwheel #piggyback

The language #Clojure and #ClojureScript languages are so stable, with breaking changes being frowned upon in the culture. But breaking in the (frankly, awesome!) tooling has been my difficulty as I maintain a dozen projects of varying ages. It is a real problem. #cider #nrepl #figwheel #piggyback

The language #Clojure and #ClojureScript languages are so stable, with breaking changes being frowned upon in the culture. But breaking in the (frankly, awesome!) tooling has been my difficulty as I maintain a dozen projects of varying ages. It is a real problem. #cider #nrepl #figwheel #piggyback

Blogged: ClojureScript REPL Workflow with Figwheel https://www.mikkokoski.com/blog/clojurescript-repl-workflow-with-figwheel/index.html

#clojurescript #repl #figwheel

Blogged: ClojureScript REPL Workflow with Figwheel https://www.mikkokoski.com/blog/clojurescript-repl-workflow-with-figwheel/index.html

#clojurescript #repl #figwheel

@seancorfield @datenschauer Not too many gotchas; things worked pretty smoothly.

One issue we debugged quite a bit was due to the difference in how version conflicts are resolved in deps vs lein. This resulted in ring version mismatches.

Another thing my colleague had to deal with recently is that #figwheel + deps doesn't seem to have out-of-the-box support in Cursive.

@seancorfield @datenschauer Not too many gotchas; things worked pretty smoothly.

One issue we debugged quite a bit was due to the difference in how version conflicts are resolved in deps vs lein. This resulted in ring version mismatches.

Another thing my colleague had to deal with recently is that #figwheel + deps doesn't seem to have out-of-the-box support in Cursive.

@seancorfield @datenschauer Not too many gotchas; things worked pretty smoothly.

One issue we debugged quite a bit was due to the difference in how version conflicts are resolved in deps vs lein. This resulted in ring version mismatches.

Another thing my colleague had to deal with recently is that #figwheel + deps doesn't seem to have out-of-the-box support in Cursive.

@seancorfield @datenschauer Not too many gotchas; things worked pretty smoothly.

One issue we debugged quite a bit was due to the difference in how version conflicts are resolved in deps vs lein. This resulted in ring version mismatches.

Another thing my colleague had to deal with recently is that #figwheel + deps doesn't seem to have out-of-the-box support in Cursive.

@yogthos How do you run the tests automatically, #figwheel has a way to run the tests in a browser and get notifications, is there something to do that with #shadow-cljs ?

@yogthos How do you run the tests automatically, #figwheel has a way to run the tests in a browser and get notifications, is there something to do that with #shadow-cljs ?

Hadn't done any #ClojureScript development in months. First thing that hit me coming back is how #figwheel is still magic.

I have no idea how other toolchains get by without it.