oh nevermind. I had forgotten that I had added a devtools server to one of my other builds 🙂

seeing the list of HTTP servers in the logs and being able to click on them is nice. (one is a test build, the other an ordinary :browser build)

FileNotFoundException target/shadow-node-repl.js (No such file or directory) java.io.FileInputStream.open0 (FileInputStream.java:-2) when I tried to start shadow-cljs node-repl

Another question: I add :nrepl {:port 8202} to my shadow-cljs.edn, but it tells me failed to require macro-ns "cljs.repl", it was required by "cljs.repl" when I shadow-cljs watch app

The project is here ： https://github.com/cmal/d3-cljs

@cmal ah doh. should be fixed in [email protected]. I bumped the closure compiler version yesterday but cljs.closure (used by cljs.repl) is not compatible with that.

Thanks @thheller.

both are the same problem?

yes

Hi, @thheller. shadow-cljs watch app works now.

user> (shadow.cljs.devtools.api/nrepl-select :d3-cljs)
To quit, type: :repl/quit
[:selected :d3-cljs]
cljs.user> (defn hello [who]
  (str "Hello, " who "!")
  "ret value")
There is no connected JS runtime.
cljs.user> (cemerick.piggieback/cljs-repl :d3-cljs)
There is no connected JS runtime.
cljs.user> (shadow.cljs.devtools.api/nrepl-select :d3-cljs)
There is no connected JS runtime.
cljs.user> 

I use Emacs and follows the instructions on github repo, but the repl seems not work.

There is no connected JS runtime. means that you need to open the app in the browser

I use cider in Emacs

and cider-connect to 8202

yes

`user> (shadow.cljs.devtools.api/nrepl-select :d3-cljs)

notice the user>. you were in a CLJ REPL

yep

nrepl-select causes it to switch to a CLJS REPL

cljs.user> (defn hello [who]
  (str "Hello, " who "!")
  "ret value")
There is no connected JS runtime.

and then I go into a cljs.user> repl

this then fails because there is no JS “host” connected

ie. in a :browser build you need to open it

I am in a :node-library build

in :node-library you need to run node

or use node-repl directly, that launches a node process for you

ok

you mean shadow-cljs node-repl or node-repl in Emacs?

There is no connected JS runtime. [:node-repl] Configuring build. [:node-repl] Compiling ... [:node-repl] Build completed. (39 files, 19 compiled, 0 warnings, 10.58s) JS runtime connected.

unfortunately you need to launch shadow-cljs node-repl outside of emacs

it works

but you can then (shadow.cljs.devtools.api/nrepl-select :node-repl) in emacs

JS runtime connected.
cljs.user>  (defn hello [who]
  (str "Hello, " who "!")
  "ret value")
There is no connected JS runtime.
cljs.user> 

`cljs.user> (shadow.cljs.devtools.api/nrepl-select :node-repl) There is no connected JS runtime.`

note the cljs.user> prompt. you are already in a CLJS REPL. nrepl-select ONLY works in CLJ REPLs

type :repl/quit to get back to a CLJ REPL

cljs.user> :repl/quit
:repl/quit
user> (shadow.cljs.devtools.api/nrepl-select :node-repl)
To quit, type: :repl/quit
[:selected :node-repl]
cljs.user>  (defn hello [who]
  (str "Hello, " who "!")
  "ret value")
#'cljs.user/hello
cljs.user> 

yes!

Thanks a lot. @thheller 😢 '

I’ll change that behaviour so that you can only nrepl-select when the runtime is already connected

too confusing otherwise

Thanks.

Are there any examples for building tests of :node-library project in shadow-cljs?

what do you mean by tests?

I want to write test like in lein test using cljs.test

like deftest and then run-tests

for a node library

(ns demo.app-test
  (:require [cljs.test :refer (deftest is)]))

(deftest some-demo-test
  (is (= 1 2)))

put that in test/demo/app_test.cljs, add :source-paths ["src" "test"]

shadow-cljs test

Thanks !

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

that command needs a lot of work though

its only a proof of concept at the moment

OK!

@thheller the advanced compilation change sounds great

Btw we are also interested in running the tests, that is the only problem we have now, because currently we use lein doo

https://github.com/thheller/shadow-cljs/search?utf8=%E2%9C%93&q=babel&type=

shadow-cljs depends on babel... which is unexpected

Noticed that since we have unstable network in China...

=>> yarn
yarn install v1.3.2
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
info There appears to be trouble with your network connection. Retrying...

[2/4] 🚚  Fetching packages...
verbose 27.931 Performing "GET" request to "".
[################################################] 188/189

Started using shadow-cljs last night. I wish I would have found it sooner! I can suddenly use npm deps that wouldn’t work with :npm-deps!

One question: is there programmatic access to the Java apis? I’m curious if I can keep the watcher/builder in the same JVM instance as my application’s REPL (clojure).

yes there is but it has pretty steep dependency requirements

so you need to be running clojure 1.9

beyond that shadow-cljs compile app is the same as calling (shadow.cljs.devtools.api/compile :app)

the (shadow.cljs.devtools.server/start!) fn starts the embedded server

Okay, interesting.

stop! does the shutdown

I wonder if that would work as a boot task (which can use instantiate separate instances/versions of Clojure through the “pod” abstraction)

I do recommend running it standalone though since its much more optimized that way

I do not recommend boot at all. they do a bunch of stuff that really get in the way, ie. caching doesn’t work.

Okay, gotcha

but I don’t know much about boot so maybe you can figure it out so it works properly

everything I tried just didn’t seem like a good fit at all

Yeah, I’m sure that boot could be used, but if its optimized for cli usage, that seems like the place to start

@jiyinyiyong yes it uses babel-core to transpile ES6 in node_modules.

I’m wanting to minimize friction on a team of folks who are used to lein repl and then a (start) command that does everything, including figwheel

yeah you can do that if you like, just not recommended.

Cool. Thanks for your help!