Dusk seems to be failing about vscode-laravel-artisan HOT 7 CLOSED

Once you run the command, if you look at the Output tab and select Laravel Artisan from the drop down menu, you will see all the output including errors. You may also be able to look at the developer console and possibly see output there as well.

from vscode-laravel-artisan.

My bad, I didn't know about the drop down menu for the output.

This is what I have:

[CMD] php "/Users/guill/Development/hq.sleeplessmind.com.mo/artisan" dusk  --without-tty
[ERROR] Could not open input file: vendor/phpunit/phpunit/phpunit

The path to phpunit is set in DuskCommand.php

protected function binary()
    {
        return [PHP_BINARY, 'vendor/phpunit/phpunit/phpunit'];
    }

This is where the problem is coming from. Running dusk out of the root doesn't work, which is why the dusk command from your extension doesn't work. Any work we can do on that?

from vscode-laravel-artisan.

The reason it is run from the root, is because commands don't get executed from the root of the project, so the command php artisan xxx fails saying:

Could not open input file: artisan

I could try prefixing the command to go to the project root before running the command.

from vscode-laravel-artisan.

Here is a packaged version. Could you please test and see if it fixes your issue:

laravel-artisan-0.0.17.vsix.zip

from vscode-laravel-artisan.

Thanks!

Doesn't seem to work. The first time I run Artisan: run command I have vscode telling me that it cannot run the artisan.run.command command. Then on the next calls, nothing happens. Output and debug console are empty, no task related to laravel artisan.

from vscode-laravel-artisan.

I have pushed some changes to the marketplace, it could have fixed this issue. Please let me know.

from vscode-laravel-artisan.

Closing due to inactivity.

from vscode-laravel-artisan.