How do I configure a script with project, supporting files, etc so it can be run from the PATH?

[TuggyNE]

I have several scripts I'm writing that are intended to be used like normal commands. The shebang is easy enough: #!/usr/bin/env bb. But they rely on cprop/cprop, which introduces data file dependencies (bb.edn and config.edn) that should be in the same directory as the script. bb.edn looks like this:

{:paths ["."]
 :deps {org.babashka/spec.alpha {:git/url "https://github.com/babashka/spec.alpha"
                                 :git/sha "1a841c4cc1d4f6dab7505a98ed2d532dd9d56b78"}
        org.clj-commons/clj-http-lite {:mvn/version "1.0.13"}
        com.cognitect/anomalies {:mvn/version "0.1.12"}
        cprop/cprop {:mvn/version "0.1.19"}
        failjure/failjure {:mvn/version "2.2.0"}
        zprint/zprint {:mvn/version "1.2.5"}}}

This works fine if I'm running it from the same directory, e.g. ./script.clj. But it fails (Message: Could not find namespace: cprop.core.) if I run from PATH, e.g. (in another directory) script.clj. So clearly bb.edn is not even being read. How should I fix this?

Unlike in https://clojureverse.org/t/help-utilizing-babashka-tasks-globally/8026/2, there are multiple bb.edn files (for good reason) in different directories, all of which are on the PATH.

[borkdude]

@TuggyNE This is where bbin comes in:

https://github.com/babashka/bbin

[borkdude]

@TuggyNE Another thing that's missing: you may have to move any dependencies to deps.edn and then refer to your local deps edn from the bb.edn:

In bb.edn:

{:deps {my/project {:local/root "."}}}

In deps.edn:

{:deps ...}

[borkdude]

@TuggyNE If you're not able to solve it, could maybe make a repro project, that I can clone locally? This way I can see better what should be done.

[TuggyNE]

@borkdude Looks like adding :deps {script/script {:local/root "."}} :bbin/bin {script {:main-opts ["-f" "script.clj"]}} does the job (and all of those are required, including the redundantly-qualified symbol in :deps and the unqualified symbol in :bbin/bin), but rewriting all the EDN files and also adding support for running bbin on all of them is probably more work than just setting up a simple wrapper script.

[borkdude]

OK, I'm evaluating the option that babashka should always consider the bb.edn relative to a script, in precedence over the bb.edn in the current working directory. That is the same behavior of Node.js and might make sense for scripting tools like bb. This would also simplify your problem.

[TuggyNE]

Yeah, I can't speak to any breaking changes (in that I am struggling to imagine any vaguely legitimate situation where two bb.edn files would need to be evaluated with the one in $PWD before the one in $PATH), but it would absolutely make more sense to me to have this changed.

[borkdude]

A solution without bbin is the following:

Write a bash wrapper script, e.g.

#!/usr/bin/env bash

bb --config ~/my_project/bb.edn ~/my_project/script.clj

Make that bash wrapper script executable and put it on your path.

[borkdude]

@TuggyNE So this solved your problem, right?