Yeah @thheller, let me try that, I tried “aws-sdk/config” but that didn’t do it

Hey all, is there any good docs/tutorial on using shadow-cljs to write a command line tool?

@joshua.d.horwitz I don't know of one specifically, but you should be able to do this fairly easily by generating a node script build and wrapping it with nexe - Node script build: https://shadow-cljs.github.io/docs/UsersGuide.html#target-node - nexe: https://github.com/nexe/nexe

Thank you @daviwil

hi! How can I require some dependency, for example, cljs.spec.test.alpha only in :dev mode? I need this dependency not to be in release bundle.

@y.khmelevskii people generally only require cljs.spec.test.alpha in test namespaces and not your regular ones

otherwise you can use this https://shadow-cljs.github.io/docs/UsersGuide.html#_conditional_reading

@eoliphant its probably aws-sdk/lib/config

thank you @thheller. But I can’t do something like this:

#?@(:dev [[cljs.spec.test.alpha]])

do you actually require cljs.spec.test.alpha in any of your main namespaces though?

or just in test namespaces that aren't actually used by your normal build?

is there any way to get verbose compile output? compilation is hanging and i'm having trouble figuring out where the issue is.

shadow-cljs compile your-build --verbose

thanks

let me know if you need help. compilation should never hang. it may just take a while if you use a lot of JS deps.

cool, that at least narrowed it down to the file that's causing it

does it actually hang or just compile forever? I have never had any reports of a hanging compilation

compile forever might be more accurate

i think i've narrowed it down to a macro

maybe its expanding infinitely

its stuck compiling one of my source files and maxing out my cpu

yeah sounds like a loop