1
votes

I'm following the laravel docs and trying to install a fresh installation of Laravel with the following command:

laravel new pathology-lab

When I run this command I get the following error:

enter image description here

There is no vendor directory created. I had to run composer install to install laravel dependencies.

But the Laravel docs says that with laravel new command the dependent packages are automatically installed:

enter image description here

Am I doing anything wrong? or Is there any problem with my Composer/Laravel Installer?

I'm able to install Laravel without any errors through Composer:

composer create-project --prefer-dist laravel/laravel blog

1
I guess laravel new is just buggy, it doesn't work for me too and I always use composer to create new Laravel projects.Alexey Mezenin
Did you run composer global require "laravel/installer" ?Islam Al-Rayan
yes. I've run that command. The 'laravel new' command has worked properly in the past. Last time I ran that command was a month back and it worked perfectly.Raghav
You can also create the project using composer composer create-project laravel/laravel myProjectNameAngad Dubey
I'm voting to close this question as off-topic because this is a bug report, please report your bug in the official Laravel issue trackers.Wouter J

1 Answers

0
votes

To answer your question, no, you're not doing anything wrong. You're correct about the intended function of laravel new blog and the auto-installation of dependencies. I would recommend that you submit this as a bug report or fix the issue and submit a pull request.

This is also a very dated question, and for new people coming across it from Google, it's very unlikely that this bug still exists, and updating to the latest version of laravel should resolve it.