Here's the whole process:

root@8dd83b662960:/var/www# rm -rf testbox
root@8dd83b662960:/var/www# box install
 √ | Installing ALL dependencies
   | √ | Installing package [forgebox:testbox@^4.5.0+5]
   |   | √ | Installing package [forgebox:cbstreams@^1.5.0]
   |   | √ | Installing package [forgebox:mockdatacfc@^3.3.0+22]
root@8dd83b662960:/var/www# echo $?
0
root@8dd83b662960:/var/www# ls testbox/
Application.cfc  apidocs  box.json  changelog.md  license.txt  readme.md  system  test-browser  test-harness  test-runner  test-visualizer  testbox-4.5.0+5-202112132349  tests
root@8dd83b662960:/var/www# rm -rf testbox
root@8dd83b662960:/var/www# mkdir testbox
root@8dd83b662960:/var/www# touch testbox/foo
root@8dd83b662960:/var/www# box install
 √ | Installing ALL dependencies
   | √ | Installing package [forgebox:testbox@^4.5.0+5]
root@8dd83b662960:/var/www# echo $?
0
root@8dd83b662960:/var/www# ls testbox/
foo
root@8dd83b662960:/var/www#

In summary: • install with no

testbox

dir: A-OK. This is the baseline control • get rid of that, create a

testbox

dir and put any file in it • re-run the install • no problem indicated (eg:

$?

is

0

) • no install I'm fine with it not installing if the dir is there and has shiz in it. I'm not so fine that it still indicates there was no problem. And it actually indicates it did install (ie:

√ | Installing package [forgebox:testbox@^4.5.0+5]

, note the

√

)

My immediate situation was entirely contrived (albeit by accident), so it's not holding me up. But I don't think this is behaviour one ought to expect..?