After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
To use Composer is sometimes complicated. Especially for beginners.
Composer needs much resources. Sometimes they are not available on a simple webspace.
If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?
Informations about the package collect
Collect - Illuminate Collections
Deprecated: With the separation of Illuminate's Collections package, Collect is no longer necessary :tada: . We will maintain it for the 8.0 and 9.0 releases of Laravel for the convenience of package maintainers, and will stop mirroring new major versions after 9.0, but keep the existing package here for continued support.
If you are a developer working on Collect and you're tasked with upgrading it to mirror a new version of Laravel, run ./upgrade.sh from the root directory. You can pass a parameter to target a specific Laravel version (e.g. ./upgrade.sh 5.7.10) or, if you don't pass a parameter, the script will find the latest tagged release and run against that.
The upgrader will pull down the appropriate source and test files for the specified version of Laravel and then run the tests.
The upgrade script requires the use of wget. It's recommended to install homebrew, and run brew install wget
Due to a dependency on Carbon, tests won't pass until you've run ./upgrade.sh at least once locally.
Has this ever, or will it ever, develop independently from Illuminate's Collections?
No. Using an upgrade script, it's split automatically with every Laravel release to keep it in sync with Laravel's Collections, even mirroring the release numbers.
Why is the package tightenco/collect instead of illuminate/collect?
It's not an official Laravel package so we don't want to use the Packagist namespace reserved by Laravel packages. ~One day Collection may be extracted from illuminate/support to a new package. If so, we'll deprecate this package and point to the core version.~ Now that illuminate/collections has been released, we're deprecating this package.