I also want to offer a proper debugger with associated REPL.

I’d also like to build a bunch of tooling specifically for React Native, which I think is very exciting. Things like debug-on-device etc

yeah, react native is promising

And most importantly, have all that be easy to use.

also there will be need for tooling around om.next I think (graph-ql/datalog-related stuff)

Long term pipe dreams include a runner like http://wallabyjs.com/

Yes, absolutely.

ah, didn’t know about wallabyjs, thanks

good ideas, but those are mostly incremental things, testing is important but quite advanced topic, IMO to really attract masses from javascript world we need something as cool as figwheel, I mean some tool with “rails” effect

maybe room for some library, not really a tool

Right. I’m also not sure how much JS devs will want to come to an IDE since they’re more used to text editors in general.

I don’t know how many would want to use a debugger in the IDE rather than the browser, for example.

Also, don’t underestimate the value of incremental improvements, I think that the various paper cuts involved with getting started could seriously hinder adoption.

indeed

In general, after having spoken to various people who have switched from Emacs or whatever, I’m starting to think that I should have “Just works, and stays working” at the top of my feature list on the landing page

It’s a huge deal for people.

good point, you sure should focus on people who are already sold on Clojure/Script and provide solid stable PRO tool for them, I think. but there is a funnel, you also need fresh people who get converted to Clojure to later become your potential users whole funnel is somewhat important IMO

No more "I came to work on Monday, tried to fire up a REPL, and it took me until 2pm to get a working environment"

@darwin: Yes, particularly for me since I think a lot of the consistency (or not) of licence sales will be down to community growth.

@cfleming: Just something I wish Cursive had...Is jumping into multimethod impls in the Cursive pipeline? with a small contextual popup allowing to pick which impl.

I don't know if it's intended, but if I try to open a folder with a malformed (or empty) project.clj, cursive throws an exception and doesn't open the project

its

it's a little annoying as I have to fix the project.clj with a different editor

I have a project set up with CIDER, nREPL, Figwheel, and Piggieback. Using lein repl and CIDER, I can run a REPL and then start a ClojureScript REPL via Figwheel-sidecar. This works in Cursive too, for me. For a coworker, it doesn't. Trying to start the ClojureScript REPL prints INFO: nREPL connection found but unable to load piggieback. Starting default REPL

After that, the Cursive REPL will not evaluate anything.

As I said, it works (in Cursive) for me. Just not for him.

Any suggestions?

We both have latest intellij and latest cursive (1.1.0-15)

The error comes from https://github.com/bhauman/lein-figwheel/blob/a364ac2eb77a98bbd15bd483267c4f3f97cb5767/sidecar/src/figwheel_sidecar/repl.clj#L143

@stuartsierra: That’s very strange, I’ve never seen that error.

as far as I know, we have the same project configuration.

Sadly, it’s not very informative about what the error actually is.

yes

If I had to guess, I’d say piggieback is not on the classpath somehow.

Can you see it in the classpath printed on REPL startup?

good question. Will check.

@stuartsierra: If you can’t work the problem out, a workaround would be to start the REPL on the command line, and then connect from Cursive using the remote REPL option.

Ah, interesting. Thanks @cfleming

The remote option is only nREPL right now, socket REPLs coming soon.

Looking forward to Socket REPL in general.

Yes, it’s going to be nice. It’s a little tricky to present to the user since there are lots of possible configuration types over it.

i.e. pure streaming or RPC style, both can be run over it and the user will have to select that. It’s going to require a level of understanding by the user of what’s going on under the hood.

Aha! It's something in my ~/.lein/profiles.clj that makes it work.

Adding [cider/cider-nrepl "0.10.2"] to the :plugins in project.clj makes it work. No idea why yet.

And cider-nrepl automatically adds :repl-options {:nrepl-middleware [cemerick.piggieback/wrap-cljs-repl]} to the project configuration.

Which is necessary to make Piggieback work.

Hmmm

I guess you can add that manually if you don’t want to use cider-nrepl

Yes, that's what I'm doing.

It's even documented (!) https://github.com/cemerick/piggieback#installation

In the past, there have been some conflicts with cider-nrepl - I fixed a bunch of them, but it’s a fast-moving target

Wat

Wonders will never cease

Thanks for the help @cfleming.

@stuartsierra: No problem, I didn’t actually do much in the end

But I’m glad it’s working.