Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

PeterWilliam's avatar

Error: There are no commands defined in the "blueprint" namespace.

Hi there,

I followed the instruction of the laracast filament video (episode 1: blueprint) and did these steps as shown in the video:

Laravel new myproject (no starterkit, mysql, pest, no migrations have been running yet) cd myproject composer require -W --dev laravel-shift/blueprint (like shown on the blueprint website) php artisan blueprint:new

Now this error is shown: ERROR There are no commands defined in the "blueprint" namespace.

Am I missing something? Any help highly appreciated. Thank you all. Best regards Peter

0 likes
3 replies
LaryAI's avatar
Level 58

Hi Peter,

The error you're encountering, "There are no commands defined in the 'blueprint' namespace," typically indicates that the Blueprint package is not properly registered or installed in your Laravel project. Here are a few steps to troubleshoot and resolve this issue:

  1. Ensure the Package is Installed Correctly: First, make sure that the laravel-shift/blueprint package is installed correctly. Run the following command to check if the package is listed in your composer.json file:

    composer show laravel-shift/blueprint
    

    If the package is not listed, you may need to reinstall it:

    composer require --dev laravel-shift/blueprint
    
  2. Check the Service Provider: Laravel should automatically discover the service provider for Blueprint. However, if it is not working, you can manually add the service provider to the config/app.php file. Add the following line to the providers array:

    'providers' => [
        // Other service providers...
        Blueprint\BlueprintServiceProvider::class,
    ],
    
  3. Clear and Cache Configurations: Sometimes, Laravel's cached configurations can cause issues. Clear and cache the configurations using the following commands:

    php artisan config:clear
    php artisan config:cache
    
  4. Check for Command Availability: After ensuring the package is installed and the service provider is registered, check if the Blueprint commands are available:

    php artisan list
    

    Look for the blueprint namespace in the list of commands.

  5. Run the Blueprint Command: Finally, try running the Blueprint command again:

    php artisan blueprint:new
    

If you follow these steps and still encounter issues, please provide more details about your environment (e.g., Laravel version, PHP version) so that we can further assist you.

Best regards, LaracastsGPT

2 likes
PeterWilliam's avatar
PeterWilliam
OP
Best Answer
Level 1

Found a "bug". Not sure about that. The video says: composer require --dev laravel-shift/blueprint whereas the blueprint website says: composer require -W --dev laravel-shift/blueprint

Installing with the command from the video worked for me. Installing with the command from the blueprint website ended up with the mentioned error.

I don't understand what's going on there but I hope this helps someone...

Regards Peter

1 like
Snapey's avatar

Installing with the command from the video worked for me. Installing with the command from the blueprint website ended up with the mentioned error.

The option -W updates any dependencies of the package being required.

It probably displayed some error that you have not noticed, because the result was that the package did not get installed.

Please or to participate in this conversation.