> It sounds like creating a workspace.develop or nimble.develop in a parent > directory would support that workflow?
And creating nimble package for every single small script that I compile, yes. `nim c` does not understand new develop configurations, and it should not, `--nimblePath` is dumb but convenient enough for common use, everything else can be put in nim.cfg managed by nimble. See <https://github.com/nim-lang/RFCs/issues/398> "Streamline nimble-tooling interaction." section.
