Palzin Track
Get 15% off with code PTRACKSIGNUP15 

Laravel Diary Logo

Tools & Packages

tooling
Table of Contents

Prefer to use built-in Laravel functionality and community packages instead of using 3rd party packages and tools. Any developer who will work with your app in the future will need to learn new tools. Also, chances to get help from the Laravel community are significantly lower when you're using a 3rd party package or tool. Do not make your client pay for that.

Authorization | Policies | Entrust, Sentinel and other packages Compiling assets | Laravel Mix | Grunt, Gulp, 3rd party packages Development Environment | Laravel Sail, Homestead | Docker Deployment | Laravel Forge | Deployer and other solutions Unit testing | PHPUnit, Mockery | Phpspec Browser testing | Laravel Dusk | Codeception DB | Eloquent | SQL, Doctrine Templates | Blade | Twig Working with data | Laravel collections | Arrays Form validation | Request classes | 3rd party packages, validation in controller Authentication | Built-in | 3rd party packages, your own solution API authentication | Laravel Passport, Laravel Sanctum | 3rd party JWT and OAuth packages Creating API | Built-in | Dingo API and similar packages Working with DB structure | Migrations | Working with DB structure directly Localization | Built-in | 3rd party packages Realtime user interfaces | Laravel Echo, Pusher | 3rd party packages and working with WebSockets directly Generating testing data | Seeder classes, Model Factories, Faker | Creating testing data manually Task scheduling | Laravel Task Scheduler | Scripts and 3rd party packages DB | MySQL, PostgreSQL, SQLite, SQL Server | MongoDB

::Share it on::

Comments (0)

What are your thoughts on "Tools & Packages"?

You need to create an account to comment on this post.

Related articles