Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running "laravel new [name]" && running composer run dev trigger error #365

Closed
anubus298 opened this issue Nov 17, 2024 · 0 comments · Fixed by #366
Closed

Running "laravel new [name]" && running composer run dev trigger error #365

anubus298 opened this issue Nov 17, 2024 · 0 comments · Fixed by #366
Labels

Comments

@anubus298
Copy link

anubus298 commented Nov 17, 2024

Laravel Project Setup Log and Issues

Installation Steps

  1. Installed Composer, PHP, and Laravel Installer using the following command (Windows):

    Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://php.new/install/windows'))
  2. Created a new Laravel project using:

    laravel new [project-name]
  3. Selected the following options during setup:

    • Starter Kit: Breeze
    • Frontend Framework: React
    • Language: TypeScript
    • Database: MySQL
  4. Ran the following commands to complete the setup:

    cd [project-name]
    npm install
    npm run build
    composer run dev

Log Output

npx concurrently -c "#93c5fd,#c4b5fd,#fb7185,#fdba74" "php artisan serve" "php artisan queue:listen --tries=1" "php artisan pail" "npm run dev" --names=server,queue,logs,vite
[queue] 
[queue]    INFO  Processing jobs from the [default] queue.
[queue]
[logs]
[logs]    RuntimeException
[logs]
[logs]   The [pcntl] extension is required to run Pail.
[logs]
[logs]   at vendor\laravel\pail\src\Guards\EnsurePcntlIsAvailable.php:15
[logs]      11▕      */
[logs]      12▕     public static function check(): void
[logs]      13▕     {
[logs]      14▕         if (! function_exists('pcntl_fork')) {
[logs]   ➜  15▕             throw new RuntimeException('The [pcntl] extension is required to run Pail.');
[logs]      16▕         }
[logs]      17▕     }
[logs]      18▕ }
[logs]      19▕
[logs]
[logs]   1   vendor\laravel\pail\src\Console\Commands\PailCommand.php:46
[logs]       Laravel\Pail\Guards\EnsurePcntlIsAvailable::check()
[logs]
[logs]   2   vendor\laravel\framework\src\Illuminate\Container\BoundMethod.php:36
[logs]       Laravel\Pail\Console\Commands\PailCommand::handle(Object(Laravel\Pail\ProcessFactory))
[logs]
[logs] php artisan pail exited with code 1
[server]   Failed to listen on 127.0.0.1:8000 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8001 (reason: ?)
[vite] 
[vite] > dev
[vite] > vite
[vite]
[server]   Failed to listen on 127.0.0.1:8002 (reason: ?)
[vite] 'vite' n’est pas reconnu en tant que commande interne
[vite] ou externe, un programme exécutable ou un fichier de commandes.
[vite] npm run dev exited with code 1
[server]   Failed to listen on 127.0.0.1:8003 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8004 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8005 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8006 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8007 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8008 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8009 (reason: ?)
[server]   Failed to listen on 127.0.0.1:8010 (reason: ?)
[server] php artisan serve exited with code 1
@crynobone crynobone transferred this issue from laravel/framework Nov 18, 2024
crynobone added a commit that referenced this issue Nov 18, 2024
fixes #365

Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
crynobone added a commit that referenced this issue Nov 18, 2024
fixes #365

Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
@crynobone crynobone added the bug label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants