I haven't seen that before and I just ran a fresh install of the development branch without any issues. I imagine Taylor is changing tome things in preparation for the release. Try it again and see if the error still persists.
Yep you're right a composer update fixed the issue - bad timing I guess
I also get same error... composer update don;t fix it..
any new idea?
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast