sup! when I switched to Lein following the user guide, I noticed I also had to manually include the same clojure/script jars as shadow-cljs in the dependencies did I do something wrong?

after specifying them directly, the scripts began working again

Hi, Is there a way to get an env var define in the console (e.g. export URI=http://uri) in the shadow-cljs.edn for compilation ? I use it closure-defines to pass it to cljs code Thanks

If possible i would like something like that

May be i could do this with https://shadow-cljs.github.io/docs/UsersGuide.html#clj-run

@ouvasam it is not recommended to use env vars during compilation since that suggests that you actually want to do runtime configuration during compilation

you could instead call your.app.init("") to initialize your app

that means you can change the URI without actually recompiling your code

other than that you can use :closure-defines {foo.bar/uri #shadow/env "URI"} so use env vars in the config

but that is not recommended

@joao.paulo.silvasouza it is sometimes required to pin clojure/script versions when using lein yes. not doing it wrong as you are otherwise relaying on a bit of randomness when it comes to the deps

@thheller Ok Many thanks

Good morning! What is the recommended approach for testing CLJ files with shadow-cljs? (The reason is testing a macro's helper functions)

@aisamu I typically do this with the clj REPL. not actually writing tests just evaling stuff until it looks right

otherwise you can use the clj-run stuff to call your own main function to run the tests

Great, thanks!

👋 hi everyone! Has anyone used shadow-cljs to publish something to clojars or do I need to use leiningen for this and dup the shadow-cljs.edn file -> project.clj?

@loganpowell publishing with shadow-cljs is not currently supported. project.clj + lein is easier currently IMHO

gotcha

should it be a 1:1 setup for the project.clj (i.e., can I just copy the shadow.cljs.edn file)?

I only used lein for like a week before finding shadow-cljs

(I have very little lein experience)

only need to copy your :dependencies (don't include clojurescript or shadow-cljs itself)

sweet! thank you 🙂 and thank you so much for all your work with shadow

and all your help on Slack

🙏

very welcome

are reader conditionals allowed in shadow? I'm getting an error trying to use them and just want to make sure I'm not barking up the wrong tree

yes, they are

ok

what’s the error you’re receiving?

reader conditionals only are allowed inside of .cljc files

fuck, thank you!

😄

😄 👍

there’s actually some much cooler things shadow-cljs can do with reader conditionals

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

it’s non-standard though

whoop

Hello folks! question about tooling! So say I am working against a node-script target

and I do yarn shadow-cljs watch dev

am I also unnecessarily starting the web server machinery?

(I would expect that is started in :browser targets only

if that's the case I am interested in knowing if I can save some time in startup by contributing some tweak

shadow-cljs starts a webserver for administrivia things

you probably see the log output where it’s starting it on port 9630

unless you’re also seeing something like:

shadow-cljs - HTTP server for :workshop available at 

well I do not see it so that's probably already good then

Dec 21, 2018 11:39:24 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.8.Final
Dec 21, 2018 11:39:24 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.8.Final
shadow-cljs - server version: 2.7.9
shadow-cljs - server running at 
shadow-cljs - socket REPL running on port 44729
shadow-cljs - nREPL server started on port 45909
shadow-cljs - watching build :repl

yep. the server at 9630 is a kind of admin UI for your builds

oh ok

opened a PR against shadow but I think I need some help

hmm the solution to my jack in issue was to set this in Emacs: `

(add-to-list
          'cider-cljs-repl-types
          '(my-cljs-node-repl "(do (shadow.cljs.devtools.api/node-repl :dev))"))

(for shadow + nodejs repl without needing to start it via the CLI each time)