i.e.

{:git/url    ""
                                 :sha        "36894d9fd348576e265a6c129664fba159c4b319"
                                 :exclusions [thheller/shadow-cljs]}

might seem a bit odd but I have a situation where I have code that I need to load in a local repl but ignored by shadow. I have a second source path called “generated” and that’s the only place I want shadow to find source files

normally I would do this by letting shadow control the source paths i.e. :deps false

but I am using the git dep above so I need deps.edn to load it. so now I’m stuck between 2 goals

I can’t figure out a good directory layout to get around this

another option would be to load using deps.edn but then use the shadow api to remove the “src” path before it is started

shadow-cljs.edn does not support git deps

but doesn't sound like you actually need that?

I mean just create a local checkout with whatever version you want

and add :source-paths ["src/main" "../that-checkout/src/generated"] or so?

you can still add the regular dependency as well but it will pick source files from the source path over the files in the jar

that lib doesn't have a generated dir though? not sure I get what you are after 😛

yeah I was just looking a docs and the use case is similar to https://shadow-cljs.github.io/docs/UsersGuide.html#_javascript_dialects

but that lib is cljs?

that’s an interesting idea. just checkout the git lib locally and then use shadow for deps, pointing at that dir

it’s https://github.com/ribelo/doxa but I’m using a non-master branch

ok. I’ll try a local checkout. that would be a simple/easy fix until doxa gets a clojars release

thanks! I’ll report back here

@U05224H0W I found a better solution. as long as none of the source files in “src” are required, they are ignored by shadow compile. in this way I can use deps :true and include both source paths without cljs complaining

well, yes shadow only ever compiles files that are actually :require'd somewhere