-
-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project configuration shadow-cljs + deps.edn
doesn't work
#1253
Comments
One thing worth mentioning - if |
Hmm, are you referring to the warning:
? It might be that shadow-cljs is ignoring the dependency, but that it still triggers its behaviour to load cider-nrepl things to the REPL. Things do work as expected from a Calva perspective. I think we need @thheller's guidance here. |
Yeah, that's what I meant. |
I agree it is very confusing. Let's hope there is a way we can get rid of the warning. Calva is a cider-nrepl client. That's what is meant with Distilled from CIDER. |
I don't know what you are talking about. The above warning you get when you configure I don't know what else you are refering to here. Running shadow-cljs with |
@p-himik |
@thheller We get the warning when injecting the cider-nrepl dependency using the {:deps true
:dev-http {8080 "target/"}
:builds {:app {:output-dir "target/"
:asset-path "."
:target :browser
:modules {:main {:init-fn app.main/main!}}
:devtools {:after-load app.main/reload!}}}} And this {:paths ["src"]
:deps {thheller/shadow-cljs {:mvn/version "2.15.2"}}} Then starting the REPL using Calva:
Everything works great, but users might be led to believe something is wrong because of that warning. |
Shall I report this as an issue on shadow-cljs? |
yes |
We should probably remove it, because it does not really make sense anyway. At least I can't figure out how it would make sense. If shadow is configured to use
deps.edn
than theshadow-cljs
project type should be used.The text was updated successfully, but these errors were encountered: