Can illuminate/console be used standalone?

[yoan-myparcel]

Hi Laravel community! I was about to file a bug report but I decided to first check if I am not misunderstanding something!

I am using illuminate/console to power a CLI application. Since it is CLI-only, I decided that a fully configured project structure build around Illuminate\Foundation\Application would be unnecessary if I can just use illuminate/console.

That I did successfully with version 9.* of the package, but I recently upgraded to 12.* and I ran into issues.

Basically, what I did until now is use Illuminate\Console\Application with a Illuminate\Container\Container, but since version 10 (apparently), a trait called ConfiguresPrompts, which is included in Illuminate\Console\Command requires a Illuminate\Contracts\Foundation\Application instead of Illuminate\Container\Container. Furthermore, the trait calls a runningUnitTests() method on the app/container (depends what you inject in the Console Application object), which fails when just using Illuminate\Container\Container (method is not defined there since it is part of another interface).

I feel like there is a type issue alone the way, but as I said above - I am not 100% sure if illuminate/console is supposed to be used in that way. The suspected type issue comes from:

• In https://github.com/laravel/framework/blob/12.x/src/Illuminate/Console/Application.php#L68 illumincate console application can be created using the Container interface. Note that this interface does not have runningUnitTests method.
• In https://github.com/laravel/framework/blob/12.x/src/Illuminate/Console/Application.php#L216-L218 the class accepts laravel Command types, and if such the setLaravel setter is called where the container injected before is passed
• Command class includes ConfiguresPrompts trait https://github.com/laravel/framework/blob/12.x/src/Illuminate/Console/Command.php#L17
• The trait calls runningUnitTests, which could or could not be part of $this->laravel

I believe the the type bug is here and here.

Example

You can find the code from this example here.

<?php
use Illuminate\Console\Application;
use Illuminate\Container\Container;
use Illuminate\Events\Dispatcher;
use Illuminate\Console\Command;

// example command
class ExampleCommand extends Command
{
    protected $signature = 'example';

    protected $description = 'Example command';

    public function handle(): int
    {
        $this->info('Hello, world!');
        return self::SUCCESS;
    }
}

// configure console application
$container = new Container();
$events = new Dispatcher($container);
$application = new Application($container, $events, '1.0.0');
$application->setName('illuminate/console: Standalone Demo');
$application->resolve(new ExampleCommand());
$application->run();

The result of running the above script is the following error:

PHP Fatal error:  Uncaught Error: Call to undefined method Illuminate\Container\Container::runningUnitTests() in /home/user/illuminate-console-standalone/vendor/illuminate/console/Concerns/ConfiguresPrompts.php:36
Stack trace:
....

Is this worthy of a bug report?

It is a the first time I write in this community, I do not often report nor I find bugs in packages I use. Is this something for what I should report a bug instead of this discussion?

[feryardiant]

You might need to check https://laravel-zero.com

[mbabker]

Personally, I gave up trying to use any of the Laravel framework code in a standalone context since the framework itself is treated as a full-stack package and standalone component use seems to be not well supported, especially given how frequently code in the framework is hard coupled to concrete implementations versus relying on only the contracts.