Closed jshwlkr closed 6 years ago
Doing a factory reset in Docker and rebuilding doesn't seem to address this issue for me.
If I go into lando ssh
and try phpunit
I get a command not found
.
If I go through the steps of adding eslint as defined in the docs, I do get access to eslint via lando eslint
.
Okay, well I don't know what to say about this. Instead of using composer directly I dropped phpunit and phpbench directly in .lando.yml and after a rebuild it looks like they work fine.
So I was missing the cmd line in the tooling entry.
cmd: /app/vendor/bin/phpunit
Is this present in all the documentation? I feel like it took some hunting to track it down.
Bug Report
Tell us about your setup
v3.0.0-beta.47 on macOS 10.13.6 (High Sierra)
Tell us about your
.lando.yml
Tell us about the command you were running
Tell us about the error you got
Tell us generally about your bug
In this case I get a not found error.
I get the equivalent error when I try
However the default commands seem to work just fine. It seems I only get an error on tooling I try to add myself.
My composer.json looks like
If I run
phpunit and phplint seem to be available
Tell us more
Does this bug prevent you from using lando? Not the problem of not being able to use phpunit, but the problem of not being able to use custom tooling definitely does.