{"id":1491,"date":"2019-09-09T07:42:50","date_gmt":"2019-09-09T07:42:50","guid":{"rendered":"https:\/\/www.nethues.com\/blog\/?p=1491"},"modified":"2022-07-21T11:41:32","modified_gmt":"2022-07-21T11:41:32","slug":"laravel-6-released-whats-new","status":"publish","type":"post","link":"https:\/\/www.nethues.com\/blog\/laravel-6-released-whats-new\/","title":{"rendered":"Laravel 6 Released: What\u2019s New?"},"content":{"rendered":"

Laravel 6.0 is here!<\/p>\n

Taylor Otwell, the creator of Laravel, had been teasing the 6.0 release for a long time and it has officially dropped.<\/p>\n

The release marks the start of the Laravel framework using\u00a0Semantic Versioning, compatibility with\u00a0Laravel Vapor, improved authorization responses, job middleware, lazy collections, sub-query improvements – to name a few. Well, that\u2019s really interesting!<\/p>\n

Let\u2019s dig a little deeper and see what Laravel 6 has in store for the users.<\/p>\n

Semantic Versioning<\/strong>
\nAlthough the jump from 5.8 to 6.0 is a major release, Otwell mentioned that in terms of new features and changes, this update will feel more like moving from 5.8 to 5.9.<\/p>\n

Laravel has had huge updates with every major version release, which is typical in a young framework. All the updates throughout 5.x laid the groundwork for a stable and robust framework. Going forward with 6.0, you won’t have to worry as much about huge breaking changes and rewrites with every new major release. Because of this new stability, the Laravel framework package is officially adopting the more traditional semantic versioning. This makes the framework consistent with the other first-party Laravel packages.<\/p>\n

Improved Authorization Responses<\/strong>
\nPreviously it was difficult to provide custom error messages around authorization to end users. Laravel 6 introduces a\u00a0Gate :: inspect\u00a0method which provides the authorization policy\u2019s response:<\/p>\n

\"Laravel<\/p>\n

Job Middleware<\/strong>
\nInstead of manually adding extra boilerplate code around your jobs, you can now\u00a0extract it into middleware\u00a0and then just attach it to the job.<\/p>\n

\"Middleware\"<\/p>\n

The middleware will help you avoid custom logic in the body of your job\u2019s\u00a0handle()\u00a0method.<\/p>\n

Lazy Collections<\/strong>
\nLazy collections are a game-changer for working with extensive collections of data, including Eloquent model collections. A new\u00a0Illuminate\\Support\\LazyCollection\u00a0class leverages PHP\u2019s generators to keep memory low while working with large datasets. Check out\u00a0Lazy Collections<\/strong>\u00a0documentation for more details.<\/p>\n

Laravel UI<\/strong>
\nThe frontend scaffolding provided with Laravel 5.x releases is now extracted into a separate\u00a0laravel\/ui\u00a0Composer<\/strong> package. This allows first-party UI scaffolding to be iterated on separately from the primary framework.<\/p>\n

In a tweet back in May, Otwell mentions that he’s considering adding a\u00a0Tailwind\u00a0option as well!<\/p>\n

\n

I\u2019ve created https:\/\/t.co\/IPvq4PdlrV<\/a> to experiment with extracting Laravel\u2019s front-end scaffolding. Give it a look! Welcome any improvements and will probably explore a @tailwindcss<\/a> option. 🔥 \u201cartisan ui vue \u2014auth\u201d \u2026 \u201cartisan ui react \u2014auth\u201d<\/p>\n

\u2014 Taylor Otwell 🏝 (@taylorotwell) May 31, 2019<\/a><\/p><\/blockquote>\n