Lambdaisland has a lib for this:

(require '[babashka.deps :as deps])

(deps/add-deps '{:deps {lambdaisland/uri {:mvn/version "1.13.95"}}})

(require '[lambdaisland.uri :as uri :refer [uri]])

(-> (uri "")
    (uri/assoc-query {:foo :bar})
    uri/uri-str prn)

@UE21H2HHD Perhaps lambdaisland/uri wants to take a logo PR ;)

Nice! Thank you very much for the complete example with add-deps and everything!

To my knowledge, bb doesn't look upwards for a bb.edn

But it works ...

It picks the bb.edn from the current working directory

if you execute <dir>/bin/my-command and you have <dir>/bb.edn that works, because <dir> is the current working directory

Shoot. Was running from the root directory, and forgot to check if it works from elsewhere. Ok, gotta fix that.

I just shouldn't multi-task.

If you want to have self-contained scripts with dependencies, you can use this: https://clojurians.slack.com/archives/CLX41ASCS/p1665143925396069?thread_ts=1665143479.202349&cid=CLX41ASCS

I ended up with:

#!/usr/bin/env bb

(require '[babashka.deps :as deps])

(let [root (-> *file*
              fs/parent
              fs/parent)
      paths [(fs/path root "src")
             (fs/path root "resources")]]
  (deps/add-deps `{:paths ~paths
                   :deps {io.github.hlship/cli-tools {:mvn/version "0.5"}}}))

(require '[net.lewisship.cli-tools :as cli])

(cli/dispatch {:tool-name "flow"
               :namespaces '[flow.commands]})

you might have to stringify those paths

It's working without doing that, haven't traced down why.

ok :)

maybe because you're not requiring anything locally

Well, it's able to load namespaces under the root src dir, so it's working for whatever reason.

nice :)

Yes, I could (map str paths) but I'm trying to keep this simple.

I enjoyed the podcast on the cognicast btw, thanks for mentioning bb

Would you consider an extra switch on bb to look upwards from the script file to find the bb.edn?

Or, I suppose, could move the bb.edn to the bin dir, but that feels dirty for some reason.

I wonder what edge cases that might introduce. clj doesn't support this either right?

No I don't think clj does this.

You can also use --config to specify an alternative bb.edn - not sure if that helps

I've tried a bunch of variations of #!/usr/bin/env bb --config "$(dirname $0)/../bb.edn" but it doesn't look like you can do a shell expansion there, so I get error Message: File does not exist: $0)/../bb.edn"

I'm also curious about the space between "full blown project in its own git repo" (at least its own folder with a bb.edn file) and "single file self contained script". I feel like I have to pick one or the other. Not that I have any solutions to suggest 😄😅

Another thing: you can re-invoke bb itself using process/exec

Or just babashka.process/shell: So instead of the shebang you could do:

(babashka.process/shell "bb" "--config" "...")

But I wonder what is the problem behind the problem here. I never have this problem since I always launch scripts from the root:

script/foo.clj
bin/foo.clj

cd bin && ./foo.clj

I think I mentioned flow in the 'cast. It's a tool I use all over the place (it's that personal tool you don't necessarily share with anyone). So I have that bin directory on my $PATH but I'm almost never in that root directory to execute it, so it has to be able to find that directory to find src , resources and dependencies.

Can you be more specific: is flow in the bin directory? And what does it do exactly, invoke bb?