@richiardiandrea what do you have in mind?

yes it has its own internal resolve mechanisms

@thheller I wanted to ask if shadow could output the classpath so that I can use lumo 🙂

so how this works internally is that shadow-cljs itself depends on shadow-cljs-jar

which is a standalone uberjar thats just used for resolving maven dependencies

https://github.com/thheller/shadow-cljs/tree/master/packages/shadow-cljs-jar

https://github.com/thheller/shadow-cljs/blob/master/packages/shadow-cljs-jar/src/shadow/cljs/npm/deps.clj

not much code at all

basically reads a edn {:dependencies [[foo/bar "1.2.3"]]} map from stdin

downloads the deps

uhm interesting

write everything to :cache-root/classpath.edn

exit with 0 on success

coool so I can use :cache-root/classpath.edn I guess

oh no yeah

https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/npm/cli.cljs#L144-L168

it is in edn format, I need to convert it

and it does not include only the build deps but also shadow deps

well you could create something like lumo deps

to build the classpath and such

well you could just use tools.deps which I would recommend at this point to be honest

yep I could, but I have already project.clj in place and I can just use lein...or use tools.deps

yeah exactly

clojure already has clojure -Spath which is what I assume you are asking for?

yep that's what I am using

so what do you need shadow-cljs for?

well, I was just wondering 😄

since I expect deps.edn to become standard pretty soon I'd suggest sticking with that

it's just that it requires to use an additional tool on ci...while shadow can be provisioned through npm install but yeah...you are probably right...

but when using shadow-cljs you'd need a shadow-cljs.edn config

since the script itself only reads from that

yep I am ok with that, but then the classpath has to be generated with other tooling

no worries Thomas, just grumbling at the some many tools to provision on CI 😄

well you could roll your own with the shadow-cljs-jar thingo

I could definitely do that

I like that you can export functions for :node-library, you could even add JSDoc 😄 😄 😄

will see if I can PR something sooner or later but shadow-cljs has improved a lot since the last time I checked!

@thheller you are awesome thanks for the fix!

last question, is there a way to use ClojureScript libraries deployed through the npm mechanism at the moment?

no

and is there a way to add things to the shadow-cljs tool classpath by any chance? my deps are not deployed on Maven as we prefer npm in my company at the moment...

oh I see I can get creative with deps.edn, I will try that

shadow-cljs can't since it loads itself via maven

I am in a monorepo so I can have a deps.edn file that contains {:paths ["src" "../spec-cljs/src"]}

and it will end up in shadow's classpath

that is what I mean by "being creative" 😄

lol other question

when I build, I see in my dist a folder called cljs-runtime

do I need to deploy both? how do I get a unique artifact?

that only happens when you set :output-dir

you can set :release {:output-to "some-other/path.js"} to only change the path for release

if you only set :output-to you will only get that file. :output-dir during development uses an absolute path in the target/shadow-cljs directory so the cljs-runtime folder doesn't show up in the dist dir 😛

Hi @thheller , I found (println "hello") will print hello in the screen I executed shadow-cljs node-repl, Is it possible to print the message in cider? (https://github.com/thheller/shadow-cljs/issues/207#issuecomment-367699962)

Like I said it is not currently possible.

I need to do some work around the node-repl with regards to nrepl

and then there are two ways the output could get there. either pipe all stdout of the managed node process to the REPL

Sorry, I've misunderstood you before. I thought you meant to let me open a new issue to discuss this issue 😂

yes thats what I meant.

discussing it here just gets lost so a ticket is better

ok, I will open a new issue later 😛

I’m getting IllegalStateException: Can't change/establish root binding of: *cljs-warnings* with set when using the [binaryage/oops] library (https://github.com/binaryage/cljs-oops) within a shadow-clj repl. Any ideas?

hmm never noticed that its messing with compiler bindings from a macro

Yeah - I pulled the library in when goog.object/set did not seem to be working to set properties of a javascript object. I believe something else is going on. My javascript interop chops are weak.

that error in particular is a bug in shadow-cljs though. or rather was. fixed in [email protected]

Excellent - thanks @thheller!

@thheller do you have any idea how hard would be to enable REPL in React Native apps? how is it currently implemented for web, websockets? having live-reload/REPL on RN would be awesome

it might work if you import "shadow-cljs/shadow.cljs.devtools.client.browser"

or wherever your :output-dir is

ideally there would be a :target :react-native but I haven't done any serious RN development

last time I tested there wasn't any way to turn of their live reloading

I didn't go past the "hello world" experience

I'm making a toy application, and to my surprise & delight I've got a user to support. My goal is for her to be able to run my server.js in node. I changed my project to use shadow-cljs, and it seems to be achieving my goal. However, I'm not sure what's going on with my tests.

I successfully compiled a test file, and ran it in node. But, my specs were not found.

which config did you use?

I'll post it, one sec

and, shadow compile test followed by a node invocation on what was generated

you said "specs"? are you using cljs.test?

yes

are the namespaces named sherman.server-test?

I doubt I have things set up 'correctly'.... I was developing by having a lein auto tach lumo process running, and I have a (cljs.test/run-tests) line at the end of each of my test files

definitely don't need the run-tests

you can put a (prn :foo) or so to confirm that they are getting loaded

shadow compile test --verbose should also show them getting compiled

what is your test namespace?

This might be easiest, altho it is a push from before I was trying shadow: https://github.com/mathpunk/sherman

The only thing that's changed since has been shadow-cljs.edn, and I've just commented out the cljs.test/run-tests

let's see what verbose compiling does...

looks fine

and... it is fine. I have no idea what that previous output was

ok, second question: is there a method for having tests run when I change code? I used to use CIDER as my test runner for Clojure, which I don't think is going to work easily in CLJS. On this project I had been running a lein auto tach lumo task in a separate window, but I'm not sure if there's a way of doing something similar in shadow yet

for node not yet

i guess third question is, should I remove my project.clj entirely? everything's being done by shadow now?

ok

you can use something like chokidar-cli

oh ok, so that will watch to see if the output test file changes... great

chokidar out/node-test.js -c 'node out/node-test.js'

npm install -g chokidar-cli https://github.com/kimmobrunfeldt/chokidar-cli

:thumbsup:

thanks so much! sorry about the first non-question, no clue what that was about

np

thanks, I'll try that out, it is possible now to disable their auto-reload

so we can do that and rely on the shadow one if that works 🙂

@thheller doens't work =/ the only thing I see is this message on the android console: I/ReactNativeJS: '%cDEVTOOLS: disconnected!', 'color: blue;

code doesn't reload, and the REPL doesn't respond as well

To quit, type: :cljs/quit
=> [:selected :app]
3
There is no connected JS runtime.

no idea. I only ever opened the iOS emulater once

won't have time to play with react-native for a while

if figwheel works then it is possible for shadow-cljs as well. just might take some tweaks.

sure, I can try to look at it, thanks for the tips

hey @thheller if i wanted to hack around a bit with the nrepl connection, what’s the best way to experiment with shadow-cljs when building from source?

I run lein with-profiles +cljs repl then (require 'repl) (repl/go)

(shadow.cljs.devtools.api/watch :browser) is the test build I commonly use

what do you want to do?

I want to debug the protorepl connection to see if I can make it do all the cool shit it is capable of, but I don’t want to bug you every single day 🙂

@thheller I see that the browser versions tries to use <script> tags to load things, that wont work on RN, I'm wondering if its easier to start from the node version, I tried that directly but seems like RN doesn't have teh crypto package, but in terms of load seems the node version is closer

last time I checked proto-repl didn't use any nrepl-middleware but rather just evals CLJ code straight up.

so that won't work for CLJS

In theory, I should be able to get function arguments to pop up as I type, get autocompletion to work, be able to jump to source, be able to get docstrings inline.

@wilkerlucio if you use :npm-module it won't use <script>

It can connect via an nrepl connection. That’s how I use it.

@lee.justin.m like I said. they do this by evaling clojure code. I think.

humm, good to know, I'll keep reading 🙂

My suspicious is that it just doesn’t even try to do the stuff that it does with the clj repl, but I really want it to. 🙂

you'll probably need to hack that on the proto-repl side

still can't get past the blasphemy that proto-repl is written in coffeescript 😛

coffeescript is a nice language. too bad I don’t know it.

nah its horrible. did it for 2 years before CLJS. never want to do it again

well okay i’ll futz around with the coffeescript side. partly i wanted to get some insight as to what the hell is going on with all these different repl techniques

it confuses the hell out of me that you can start a clj repl and then switch into a cljs-repl (like with figwheel). but then you can also connect to the same thing via a network

usually with nrepl most of the heavy listing is done by middleware. ie. cider-nrepl.

but proto repl just straight up evals CLJ code

so when you say “they do this by evaling clojure code” I don’t really know what you mean because, you know, isn’t that the “e” part of the repl?

yes and no

nrepl has two ways of doing stuff

eval is usually just for what the user types

and middleware handles tool related stuff

eg. https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/middleware/complete.clj

the middleware takes care of completion for clj and cljs

but proto-repl just sends full forms to eval

https://github.com/jasongilman/proto-repl/blob/master/lib/proto-repl.coffee#L648-L656

so, somehow in my many iterations before i landed on shadow, I was able to start protorepl and get a full feature set.

I think I did that by lein watch or whatever the command was and then (do (use 'figwheel-sidecar.repl-api) (start-figwheel!) (cljs-repl))

for CLJS?

but maybe that was when i was doing CLJ (sorry I just can’t remember)

CLJ sure

oh ok

CLJ should work just fine now

I really want to be able to make protorepl fully featured with cljs but I don’t even understand the problem. maybe after i’ve got a little more experience

from briefly going over the proto-repl sources that will be a gigantic effort

it just isn't built with CLJS in mind at all

is the issue that the nrepl channel is different from whatever its doing when you just fire up a normal repl?

no. the issue is what proto-repl is doing with the REPL.

there seems to be a gigantic discussion about this https://github.com/jasongilman/proto-repl/issues/54

yea i’ve read through that. i wanted to push it forward. maybe it isn’t possible.

it is definitely possible

but if you take a look at the completion code now

https://github.com/jasongilman/proto-repl/blob/master/lib/completion-provider.coffee#L35-L45

it evals this code in the REPL. which you can also do by hand.

this is clojure code that only gives you completions for clojure code.

you'd need to send entirely different code for CLJS

it’s painful to think that all the juicy juicy data is sitting right there in the shadow watch process and all someone needs to do is just marshall a couple of dumb op codes back and forth to get it

well cider-nrepl already has access to all the data I believe

proto-repl eval works because you just send stuff and it handles the result

that is simple

and works the same in both languages

the rest is entirely different

it seems to have special code for self hosted js