[Windows] make:livewire fails with "Undefined array key 'pages'" when using namespace syntax

[johnef]

Livewire version

v4.1.4

Laravel version

v10.50.0

Which PHP version are you using?

PHP 8.3

What is the problem?

Livewire version: v4.1.4 (also tested on v4.0.3)
Laravel version: v10.50.0
PHP 8.3
Operating System: Windows (Laragon)

Steps To Reproduce

Upgraded from Livewire 3.x to Livewire 4.x
Verify config/livewire.php has the default component_namespaces configuration with pages key
Run: php artisan make:livewire pages::posts.create
Error occurs: Undefined array key "pages"

Additional Information

The pages namespace is correctly configured and accessible via config() in Tinker
The error only occurs in the Artisan command context
Windows path separators appear mixed (\ and /) in the config output
This appears to be a Windows-specific parsing issue with the :: namespace separator

Code snippets

Config verification (works in Tinker):

> config('livewire.component_namespaces')
= [
    "layouts" => "C:\laragon\www\bex-l\resources\views/layouts",
    "pages" => "C:\laragon\www\bex-l\resources\views/pages",
  ]

How do you expect it to work?

Expected Behavior
The command should create a page component at resources/views/pages/posts/create

Please confirm (incomplete submissions will not be addressed)

• I have provided easy and step-by-step instructions to reproduce the bug.
• I have provided code samples as text and NOT images.
• I understand my bug report will be removed if I haven't met the criteria above.

[johnef]

More information about the issue

Bug Location: src/Finder/Finder.php:73 in getClassNamespace() method
Root Cause: MakeCommand::createClassBasedComponent() incorrectly calls $this->finder->getClassNamespace("pages") on line 117, but pages is a view namespace (defined in component_namespaces), not a class namespace (defined in class_namespace). The Finder maintains separate arrays for these, and pages doesn't exist in $classNamespaces.

ErrorException: Undefined array key "pages"
at vendor\livewire\livewire\src\Finder\Finder.php:73
in getClassNamespace("pages")
called from MakeCommand.php:117 (createClassBasedComponent)

[joshhanley]

@johnef thanks for reporting! Could you confirm — are you using the --class flag when running the command, or have you changed the make_command.type setting in your config/livewire.php to 'class'?

The pages namespace is a view-only namespace designed for single-file and multi-file components. With the default config (make_command.type set to 'sfc'), make:livewire pages::posts.create should go through the SFC creation path and work fine. The crash in getClassNamespace() only happens when creating class-based components.

Could you share your full config/livewire.php so we can verify?

[johnef]

Yes I did change make_command -> 'type' => 'class', and here is my full config/livewire file

<?php

return [

    /*
    |---------------------------------------------------------------------------
    | Component Locations
    |---------------------------------------------------------------------------
    |
    | This value sets the root directories that'll be used to resolve view-based
    | components like single and multi-file components. The make command will
    | use the first directory in this array to add new component files to.
    |
    */

    'component_locations' => [
        resource_path('views/components'),
        resource_path('views/livewire'),
    ],

    /*
    |---------------------------------------------------------------------------
    | Component Namespaces
    |---------------------------------------------------------------------------
    |
    | This value sets default namespaces that will be used to resolve view-based
    | components like single-file and multi-file components. These folders'll
    | also be referenced when creating new components via the make command.
    |
    */

    'component_namespaces' => [
        'layouts' => resource_path('views/layouts'),
        'pages'   => resource_path('views/pages'),
    ],

    /*
    |---------------------------------------------------------------------------
    | Page Layout
    |---------------------------------------------------------------------------
    | The view that will be used as the layout when rendering a single component as
    | an entire page via `Route::livewire('/post/create', 'pages::create-post')`.
    | In this case, the content of pages::create-post will render into $slot.
    |
    */

    'component_layout' => 'dashboards_layouts.layout.index',

    /*
    |---------------------------------------------------------------------------
    | Lazy Loading Placeholder
    |---------------------------------------------------------------------------
    | Livewire allows you to lazy load components that would otherwise slow down
    | the initial page load. Every component can have a custom placeholder or
    | you can define the default placeholder view for all components below.
    |
    */

    'component_placeholder' => null, // Example: 'placeholders::skeleton'

    /*
    |---------------------------------------------------------------------------
    | Make Command
    |---------------------------------------------------------------------------
    | This value determines the default configuration for the artisan make command
    | You can configure the component type (sfc, mfc, class) and whether to use
    | the high-voltage (⚡) emoji as a prefix in the sfc|mfc component names.
    |
    */

    'make_command' => [
        'type'  => 'class', // Options: 'sfc', 'mfc', 'class'
        'emoji' => true, // Options: true, false
        'with'  => [
            'js'   => false,
            'css'  => false,
            'test' => false,
        ],
    ],

    /*
    |---------------------------------------------------------------------------
    | Class Namespace
    |---------------------------------------------------------------------------
    |
    | This value sets the root class namespace for Livewire component classes in
    | your application. This value will change where component auto-discovery
    | finds components. It's also referenced by the file creation commands.
    |
    */

    'class_namespace' => 'App\\Livewire',

    /*
    |---------------------------------------------------------------------------
    | Class Path
    |---------------------------------------------------------------------------
    |
    | This value is used to specify the path where Livewire component class files
    | are created when running creation commands like `artisan make:livewire`.
    | This path is customizable to match your projects directory structure.
    |
    */

    'class_path' => app_path('Livewire'),

    /*
    |---------------------------------------------------------------------------
    | View Path
    |---------------------------------------------------------------------------
    |
    | This value is used to specify where Livewire component Blade templates are
    | stored when running file creation commands like `artisan make:livewire`.
    | It is also used if you choose to omit a component's render() method.
    |
    */

    'view_path' => resource_path('views/livewire'),

    /*
    |---------------------------------------------------------------------------
    | Temporary File Uploads
    |---------------------------------------------------------------------------
    |
    | Livewire handles file uploads by storing uploads in a temporary directory
    | before the file is stored permanently. All file uploads are directed to
    | a global endpoint for temporary storage. You may configure this below:
    |
    */

    'temporary_file_upload' => [
        'disk'            => env('LIVEWIRE_TEMPORARY_FILE_UPLOAD_DISK'), // Example: 'local', 's3'             | Default: 'default'
        'rules'           => null,                                      // Example: ['file', 'mimes:png,jpg'] | Default: ['required', 'file', 'max:12288'] (12MB)
        'directory'       => null,                                  // Example: 'tmp'                     | Default: 'livewire-tmp'
        'middleware'      => null,                                 // Example: 'throttle:5,1'            | Default: 'throttle:60,1'
        'preview_mimes'   => [                                  // Supported file types for temporary pre-signed file URLs...
                                                                'png', 'gif', 'bmp', 'svg', 'wav', 'mp4',
                                                                'mov', 'avi', 'wmv', 'mp3', 'm4a',
                                                                'jpg', 'jpeg', 'mpga', 'webp', 'wma',
        ],
        'max_upload_time' => 5, // Max duration (in minutes) before an upload is invalidated...
        'cleanup'         => true, // Should cleanup temporary uploads older than 24 hrs...
    ],

    /*
    |---------------------------------------------------------------------------
    | Render On Redirect
    |---------------------------------------------------------------------------
    |
    | This value determines if Livewire will run a component's `render()` method
    | after a redirect has been triggered using something like `redirect(...)`
    | Setting this to true will render the view once more before redirecting
    |
    */

    'render_on_redirect' => false,

    /*
    |---------------------------------------------------------------------------
    | Eloquent Model Binding
    |---------------------------------------------------------------------------
    |
    | Previous versions of Livewire supported binding directly to eloquent model
    | properties using wire:model by default. However, this behavior has been
    | deemed too "magical" and has therefore been put under a feature flag.
    |
    */

    'legacy_model_binding' => true,

    /*
    |---------------------------------------------------------------------------
    | Auto-inject Frontend Assets
    |---------------------------------------------------------------------------
    |
    | By default, Livewire automatically injects its JavaScript and CSS into the
    | <head> and <body> of pages containing Livewire components. By disabling
    | this behavior, you need to use @livewireStyles and @livewireScripts.
    |
    */

    'inject_assets' => true,

    /*
    |---------------------------------------------------------------------------
    | Navigate (SPA mode)
    |---------------------------------------------------------------------------
    |
    | By adding `wire:navigate` to links in your Livewire application, Livewire
    | will prevent the default link handling and instead request those pages
    | via AJAX, creating an SPA-like effect. Configure this behavior here.
    |
    */

    'navigate' => [
        'show_progress_bar'  => true,
        'progress_bar_color' => '#2299dd',
    ],

    /*
    |---------------------------------------------------------------------------
    | HTML Morph Markers
    |---------------------------------------------------------------------------
    |
    | Livewire intelligently "morphs" existing HTML into the newly rendered HTML
    | after each update. To make this process more reliable, Livewire injects
    | "markers" into the rendered Blade surrounding @if, @class & @foreach.
    |
    */

    'inject_morph_markers' => true,

    /*
    |---------------------------------------------------------------------------
    | Smart Wire Keys
    |---------------------------------------------------------------------------
    |
    | Livewire uses loops and keys used within loops to generate smart keys that
    | are applied to nested components that don't have them. This makes using
    | nested components more reliable by ensuring that they all have keys.
    |
    */

    'smart_wire_keys' => true,

    /*
    |---------------------------------------------------------------------------
    | Pagination Theme
    |---------------------------------------------------------------------------
    |
    | When enabling Livewire's pagination feature by using the `WithPagination`
    | trait, Livewire will use Tailwind templates to render pagination views
    | on the page. If you want Bootstrap CSS, you can specify: "bootstrap"
    |
    */

    'pagination_theme' => 'bootstrap',

    /*
    |---------------------------------------------------------------------------
    | Release Token
    |---------------------------------------------------------------------------
    |
    | This token is stored client-side and sent along with each request to check
    | a users session to see if a new release has invalidated it. If there is
    | a mismatch it will throw an error and prompt for a browser refresh.
    |
    */

    'release_token' => env('LIVEWIRE_RELEASE_TOKEN', 'v4.0.1'),

    /*
    |---------------------------------------------------------------------------
    | CSP Safe
    |---------------------------------------------------------------------------
    |
    | This config is used to determine if Livewire will use the CSP-safe version
    | of Alpine in its bundle. This is useful for applications that are using
    | strict Content Security Policy (CSP) to protect against XSS attacks.
    |
    */

    'csp_safe' => false,

    /*
    |---------------------------------------------------------------------------
    | Payload Guards
    |---------------------------------------------------------------------------
    |
    | These settings protect against malicious or oversized payloads that could
    | cause denial of service. The default values should feel reasonable for
    | most web applications. Each can be set to null to disable the limit.
    |
    */

    'payload' => [
        'max_size'          => 1024 * 1024,   // 1MB - maximum request payload size in bytes
        'max_nesting_depth' => 10,   // Maximum depth of dot-notation property paths
        'max_calls'         => 50,           // Maximum method calls per request
        'max_components'    => 20,      // Maximum components per batch request
    ],
];

So to make thing clear, even if I am using the 'type' => 'class', Dose php artisan make:livewire pages::posts.create --mfc can work for me?

[johnef]

Thank you for your response, dear @joshhanley . I really appreciate you taking the time to answer this. Yes, when I used the command php artisan make:livewire pages::posts.create --mfc, it worked fine.

[joshhanley]

@johnef thanks for that! I've submitted PR #9995 with a fix.