Clojurians Log v2

I’m trying to run

:test-ci {:target  :node-test
                          :output-to "out/node-test/js"
                          :autorun "true"
                          :js-options {:resolve {"devcards-marked" {:target :npm :require "marked"}
                                                 "devcards-syntax-highlighter" {:target :npm :require "highlight.js"}}}}}

[:test-ci] Compiling ...
The required namespace "devcards-marked" is not available, it was required by "devcards/util/markdown.cljs".

I have two packages, one is the app and the other is a library on which it depends. This library is actually a dual CLJ/CLJS library. For development ease with Clojure using leiningen, I can set a soft link to the library package directory from the app package directory (in the checkouts subdirectory of the app package directory). Is there a way to do something like this for development purposes with shadow-cljs where the app is a CLJS program? Or other ways to simplify development with local package dependencies?

The simplest way that I know of to get a JVM ClojureScript REPL that I can connect my editor to (basically, just a REPL without a prompt) is to start a Clojure socket REPL (e.g. via the system property) and do something like this:

((requiring-resolve 'cljs.repl/repl)
  ((requiring-resolve 'cljs.repl.browser/repl-env))
  :need-prompt (constantly false)
  :prompt (constantly ""))

@flowthing there is no cljs.repl/repl equivalent in shadow-cljs but I could add the :prompt config options. why do you not want a prompt? what editor did you use? most editors use nrepl and not many people use the socket repl at all

I use Sublime Text, I'm working on my own thing. I don't really want to use nREPL because: a) I don't actually need any of the features it offers b) I'd like to avoid the dependency if I can (and with Clojure, it's relatively easy to upgrade a Socket REPL to implement editor integration) c) it has the same problem regarding switching REPL modes

c) is fairly straightforward to handle over nrepl though

i can understand a+b. not a fan of nrepl myself.

you could use prepl but that is somewhat ugly as well

prepl only has structured output, not structured input.

:prepl {12345 :build-id} will start a prepl on port 12345 for the build-id

the input is identical to socket repl and prepl? just clojure forms?

Yep.

Or, well. This is a rather involved topic. 😛 Anyway, a :prompt option would be great, but I'm not yet sure whether I'd actually end up using it. What I'd really like is a way to run a ClojureScript REPL in a way that's agnostic to build tooling.

given how vastly different the CLJS REPL is from CLJ thats difficult

and the REPL impl in shadow-cljs is also very very different and supports many features that the default REPLs don't

the shadow.remote stuff I built might be of interest for you but thats heavily under documented and not final yet

Indeed. I do realize it might be a pipe dream, but I think I'm still going to give it a go.

I tried fixing all the REPL issues I could think of with shadow.remote and one day I'll document and publish it

but so far its only used internally for everything shadow-cljs and the REPLs do

Sounds interesting. I'd like my thing to work with just out-of-the-box ClojureScript, though.

If I start a Clojure socket REPL and send this:

((requiring-resolve 'cljs.repl/repl)
             ((requiring-resolve 'cljs.repl.browser/repl-env))
             :need-prompt (constantly false)
             :prompt (constantly ""))

Execution error (IllegalArgumentException) at shadow.build.cljs-hacks/eval24027$fn (cljs_hacks.cljc:981).

as I said .. cljs.repl/repl will never work with shadow-cljs

Well, you said there's no equivalent. 🙂 But okay, that's good to know.

I'll see where I end up with this thing, but I can make an issue about the :prompt thing if it comes to that. In any case, thanks for the help!

yeah the REPL implementations are so drastically different that I can't provide a compatible repl-env stuff

what is the issue with :prompt?

All right, that's very good to know.

I mean why is the prompt a problem?

I just meant an option to disable the prompt when calling (shadow/api :app).

yes, but why?

When I send forms to be evaluated from my editor, I don't want the prompt to show up in the evaluation results.

2.11.22 has (shadow/repl :id {:prompt false})

Wow, thank you! 🙇:skin-tone-2:

Just to demonstrate what I meant: https://tutkain.flowthing.me/before.png https://tutkain.flowthing.me/after.png The first line with => is the "prompt" (really, the namespace indicator) my client prints (disregard the namespace there, it's WIP), the second line is the prompt shadow-cljs printed. The point is just that I'd like to be sure that what I'm getting from the server is just EDN and I can control when foo=> gets printed and how.

(Well, in this case it's not just EDN because it can also be whatever stdout gets, but anyway.)

I'll stop taking up more of your time -- thanks again!

well the easy answer is "just use lein" if you have that setup anyways

shadow-cljs.edn itself doesn't support checkouts or so. you could just add :source-paths to the proper places

Sorry for confusion, I use lein for JVM code and Shadow-cljs for JS. I'll check out :source-paths and see if that can work for me. thanks!!

https://shadow-cljs.github.io/docs/UsersGuide.html#Leiningen

just let lein manage the classpath I meant. CLJS related things will still be handled by shadow-cljs

Hi all, I’m a little confused on how to best setup a new re-frame project with shadow. I used the re-frame template lein new re-frame <app-name> I see other projects set up differently and I’m wondering what is the consensus on setting this up, if any? Lastly, any reading material you could point out regarding deployment best practices.