Sometimes such things happen when you need a certain package for Laravel, and it is outdated on the packagist website for example (the author did not have time to update or forgot) and there is a more recent version on the github. I will tell you how to add a package from github.
In project root folder find file composer.json.
By default, Composer pulls in packages from Packagist so you’ll have to make a slight adjustment to your new project composer.json file. Open the file and update include the following array somewhere in the object:
"repositories": [
{
"type": "vcs",
"url": "https://github.com/coolprog/awesomelaravelpackage"
}
]
The updated composer.json file should look as follows:
{
"name": "laravel/laravel",
"type": "project",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
// here you go
"repositories": [
{
"type": "vcs",
"url": "https://github.com/coolprog/awesomelaravelpackage"
}
],
"require": {
"php": "^7.3|^8.0",
"fruitcake/laravel-cors": "^2.0",
"guzzlehttp/guzzle": "^7.0.1",
"laravel/framework": "^8.75",
"laravel/sanctum": "^2.11",
"laravel/tinker": "^2.5"
},
"require-dev": {
"facade/ignition": "^2.5",
"fakerphp/faker": "^1.9.1",
"laravel/sail": "^1.0.1",
"mockery/mockery": "^1.4.4",
"nunomaduro/collision": "^5.10",
"phpunit/phpunit": "^9.5.10"
},
// ... so on
}
Now composer will also look into this repository for any installable package. Execute the following command to install the package:
composer require coolprog/awesomelaravelpackage
I would like to thank you for the time you’ve spent reading this article. I hope you’ve enjoyed it and have learned some useful stuff regarding Laravel custom package development. Although in real life, packages can be much more complicated than this, the ideas should be more or less the same.
Similar Posts:
- How to remove a package from Laravel using composer
- how to install and use bootstrap 5 in laravel 9
- Laravel site template for VestaCP
- How To Check The Laravel Version