Laravel artisan dev Command: Server, Queue, Logs &amp; Vite | Mohamed Said        [  ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png)   Mohamed Said Laravel Backend Engineer  ](https://msaied.com) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles  ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) 

       [  ](https://github.com/EG-Mohamed)       

 [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) 

  [ home ](https://msaied.com)    [ articles ](https://msaied.com/articles)    Laravel artisan dev: Run Server, Queue, Logs, and Vite in One Command        On this page       1. [  What Is php artisan dev? ](#what-is-codephp-artisan-devcode)
2. [  Default Processes ](#default-processes)
3. [  Registering Custom Processes ](#registering-custom-processes)
4. [  Registration Methods ](#registration-methods)
5. [  Replacing a Default ](#replacing-a-default)
6. [  Inspecting and Filtering the Process List ](#inspecting-and-filtering-the-process-list)
7. [  Key Takeaways ](#key-takeaways)

  ![Laravel artisan dev: Run Server, Queue, Logs, and Vite in One Command](https://cdn.msaied.com/533/88ab98460b08aed42d6688eaa02a9620.png)

 [  Laravel ](https://msaied.com/articles?category=laravel)  #Laravel   #Artisan   #Laravel 13   #DevCommands   #Vite   #Queue  

 Laravel artisan dev: Run Server, Queue, Logs, and Vite in One Command 
=======================================================================

     10 Aug 2026      3 min read    ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp)  Mohamed Said  

       Table of contents

1. [  01   What Is php artisan dev?  ](#what-is-codephp-artisan-devcode)
2. [  02   Default Processes  ](#default-processes)
3. [  03   Registering Custom Processes  ](#registering-custom-processes)
4. [  04   Registration Methods  ](#registration-methods)
5. [  05   Replacing a Default  ](#replacing-a-default)
6. [  06   Inspecting and Filtering the Process List  ](#inspecting-and-filtering-the-process-list)
7. [  07   Key Takeaways  ](#key-takeaways)

 What Is `php artisan dev`?
--------------------------

Laravel 13.16 shipped a first-party `artisan dev` command that consolidates everything you need during local development into a single terminal session. Before this, the application skeleton wired things together with a `dev` script in `composer.json` that piped four commands through `npx concurrently`. That script still exists, but it now does nothing except delegate to the new command:

```bash
php artisan dev

```

Under the hood the command still shells out to `concurrently`, and since Laravel 13.18 it passes `--kill-others-on-fail`, so one crashing process brings down the rest instead of leaving you with a half-running stack.

Default Processes
-----------------

Out of the box, `artisan dev` starts four processes:

| Name | Command | |---|---| | server | `php artisan serve --host=localhost` | | queue | `php artisan queue:listen --tries=1 --timeout=0` | | logs | `php artisan pail --timeout=0` | | vite | `npm run dev` |

The `logs` process relies on `pcntl_fork`, so it is skipped on Windows. The `vite` process automatically detects your lockfile and uses the correct package manager—`pnpm run dev` in a pnpm project, `yarn run dev` in a Yarn project, and so on—without any configuration.

Registering Custom Processes
----------------------------

The real power comes from the `DevCommands` class, which lets you replace or extend the defaults from your `AppServiceProvider`:

```php
namespace App\Providers;

use Illuminate\Foundation\DevCommands;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        if (! $this->app->environment('local')) {
            return;
        }

        // Replace the default queue worker with Horizon
        DevCommands::artisan('horizon', 'queue');

        // Start Laravel Reverb in debug mode
        DevCommands::artisan('reverb:start --debug', 'reverb')->purple();

        // Forward Stripe webhooks via the Stripe CLI
        DevCommands::register(
            'stripe listen --forward-to '.config('app.url').'/stripe/webhook',
            'stripe'
        )->orange();

        // TypeScript type-checking in watch mode
        DevCommands::nodeExec('tsc --noEmit --watch --preserveWatchOutput', 'types')->yellow();
    }
}

```

### Registration Methods

- **`artisan()`** — prefixes the command with `php artisan`.
- **`node()`** — prefixes with the detected package manager's run command.
- **`nodeExec()`** — uses the exec variant (`npx`, `pnpx`, etc.).
- **`register()`** — accepts a raw shell command for anything else.

### Replacing a Default

Process names are identities. Registering a process with the name `queue` replaces the default `queue:listen` worker. The same pattern overrides any built-in:

```php
DevCommands::artisan('serve --host=localhost --port=9000', 'server');

```

Application-registered processes always outrank framework defaults, which in turn outrank anything registered from `vendor`.

Inspecting and Filtering the Process List
-----------------------------------------

Added in Laravel 13.17, `php artisan dev:list` prints every registered process, its command, and the file and line it was registered from—without starting anything.

You can also limit which processes run at start-up:

```php
// Only start the server and Vite
DevCommands::only('server', 'vite');

// Start everything except the queue worker
DevCommands::except('queue');

```

These are runtime filters, not deletions, so the excluded process still appears in `dev:list` and can be restored by removing one line.

Key Takeaways
-------------

- `php artisan dev` is available from Laravel 13.16 and replaces the Composer `dev` script.
- Four processes run by default: dev server, queue worker, Pail log tail, and Vite.
- Vite auto-detects npm, pnpm, Yarn, or Bun from your lockfile.
- Custom processes are registered via `DevCommands` in `AppServiceProvider`.
- Reusing a process name (e.g. `queue`) replaces the framework default.
- `php artisan dev:list` (13.17+) shows every registered process and its source location.
- `--kill-others-on-fail` (13.18+) ensures a single crash stops the entire stack cleanly.

---

*Source: [Laravel artisan dev: Run Server, Queue, Logs, and Vite — Laravel News](https://laravel-news.com/artisan-dev-command)*

 Found this useful?

          [  ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Flaravel-artisan-dev-run-server-queue-logs-and-vite-in-one-command&text=Laravel+artisan+dev%3A+Run+Server%2C+Queue%2C+Logs%2C+and+Vite+in+One+Command) [  ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Flaravel-artisan-dev-run-server-queue-logs-and-vite-in-one-command) 

 Frequently Asked Questions 
----------------------------

  3 questions  

     Q01  How do I replace the default queue worker with Laravel Horizon in `artisan dev`?        Register a process named `queue` in your `AppServiceProvider` using `DevCommands::artisan('horizon', 'queue')`. Because process names act as identities, this replaces the built-in `queue:listen` process with Horizon. 

      Q02  Does `php artisan dev` work on Windows?        Mostly yes. The `logs` process (Laravel Pail) requires `pcntl_fork`, which is unavailable on Windows, so it is skipped automatically. The server, queue, and Vite processes still run. 

      Q03  How can I see all registered dev processes without starting them?        Run `php artisan dev:list`, introduced in Laravel 13.17. It prints each process name, its command, and the file and line number where it was registered. 

  Continue reading

 More Articles 
---------------

 [ View all    ](https://msaied.com/articles) 

 [ ![Filament v4 Migrating from v3: Breaking Changes and Refactor Patterns](https://cdn.msaied.com/700/85cddaf32751d756924869323a845563.png) filament laravel upgrade 

### Filament v4 Migrating from v3: Breaking Changes and Refactor Patterns

A practical, opinionated guide to the most impactful breaking changes when upgrading Filament v3 to v4, with c...

  ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp)  Mohamed Said 

 25 Sep 2026     4 min read  

  Read    

 ](https://msaied.com/articles/filament-v4-migrating-from-v3-breaking-changes-and-refactor-patterns-1) [ ![Livewire v3 Islands, Lazy Components, and Deferred Loading in Practice](https://cdn.msaied.com/699/2667012bbe680cb54d99e4596e396547.png) livewire laravel performance 

### Livewire v3 Islands, Lazy Components, and Deferred Loading in Practice

Lazy components and deferred loading in Livewire v3 let you ship fast initial pages and hydrate expensive UI o...

  ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp)  Mohamed Said 

 25 Sep 2026     1 min read  

  Read    

 ](https://msaied.com/articles/livewire-v3-islands-lazy-components-and-deferred-loading-in-practice-4) [ ![Auto-Load Generated Columns After Save with Laravel's #[Refreshes] Attribute](https://cdn.msaied.com/697/2450936023128760d64547a61ee24087.png) Laravel Eloquent Generated Columns 

### Auto-Load Generated Columns After Save with Laravel's #\[Refreshes\] Attribute

Laravel 13.33 introduced the #\[Refreshes\] PHP attribute for Eloquent models. Declare which database-computed c...

  ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp)  Mohamed Said 

 23 Sep 2026     4 min read  

  Read    

 ](https://msaied.com/articles/auto-load-generated-columns-after-save-with-laravels-refreshes-attribute) 

   [  ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png)   Mohamed Said Laravel Backend Engineer  ](https://msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow.

Explore

- [Home](https://msaied.com)
- [Projects](https://msaied.com/projects)
- [Articles](https://msaied.com/articles)
- [Certificates](https://msaied.com/certificates)
- [Contact](https://msaied.com#contact-section)

Connect

- [   hello@msaied.com ](mailto:hello@msaied.com)
- [   +20 109 461 9204 ](tel:+201094619204)

© 2026 Mohamed Said. All rights reserved.

 [  ](https://github.com/EG-Mohamed) [  ](https://www.linkedin.com/in/msaiedm/) [  ](https://wa.me/201094619204) [  ](mailto:hello@msaied.com) [  ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)
