hey, sometimes when I start a repl connecting to a script running in :target :node-script standard out seems to be set to the node process, but I'd like it to go to the repl if possible

e.g. when running (println "hello") I'd like "hello" to show up in the repl 🙂

am I missing something obvious? what's tricky is that sometimes the text do end up in the repl...

@saikyun the only time the text ends up at the REPL is when you use node-repl (not the build repl)

https://github.com/thheller/shadow-cljs/issues/373

Is it possible to use :target :node-library with only ^:export to denote exports?

@mruzekw no. all exports must be configured but there are several options to do so

Kk, I think a default export is the closest to what I want.

Thanks

I'm trying to connect from Cursive to two repl runtimes simultaneously, both from the same build (`{:target :chrome-extension}`), one for the background script, and one for the content script. I'm able to use (shadow/repl-runtime-select ...) to switch between them, but what if I want to keep a repl open to each runtime at the same time, instead of switching?

I'm really just trying to work on the ergonomics, so if there's a different workflow approach that's great too.

I assume you already have 2 REPLs running in Cursive?

I mean connected twice?

I was doing it with a remote nREPL connection, since that seemed to play better with the Cursive tooling, but I could try two local Cursive repls.

oh wait right

yeah you can't currently switch that