A Collections-only split from Laravel's Illuminate Support
Branch: laravel-5.7-on…
Clone or download
Latest commit c1a36a2 Feb 13, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
src/Collect Laravel 5.7.25 changes Feb 5, 2019
stubs Fixes issue #92 Mar 16, 2018
tests Laravel 5.7.26 changes Feb 13, 2019
.gitignore Ignore composer.lock Jan 29, 2019
.travis.yml Test enhancement Jul 9, 2018
collect-logo.png fade that logo son May 4, 2016
composer.json Update Var-dumper constraint style per Composer docs Sep 13, 2018
phpunit.xml Merge branch 'master' of composer.lock Aug 10, 2018
readme.md Update readme.md Nov 8, 2018


Travis Status for tightenco/collect

Collect - Illuminate Collections

Import Laravel's Collections into non-Laravel packages easily, without needing to require the entire Illuminate\Support package. (Why not pull Illuminate\Support in framework-agnostic packages)

Written by Taylor Otwell as a part of Laravel's Illuminate/Support package, Collect is just the code from Support needed in order to use Collections on their own.

Lovingly split by Matt Stauffer for Tighten Co., with a kick in the butt to finally do it from @assertchris.


With Composer:

composer require tightenco/collect


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.

# or
./upgrade.sh 5.7.10

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.



  • Will this develop independently from Illuminate's Collections?
    No. Right now it's split manually, but the goal is for it shortly to be split automatically 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.
  • Why not just use an array?
    What a great question. Tighten alum Adam Wathan has a book about that.


The Laravel framework is open-sourced software licensed under the MIT license. Collect consists almost entirely of Laravel source code, so maintains the same license.