Skip to content

Instantly share code, notes, and snippets.

@othyn
Last active October 20, 2021 09:41
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save othyn/4ea6bf099fc1c70696e5dc6eaa658dbc to your computer and use it in GitHub Desktop.
Save othyn/4ea6bf099fc1c70696e5dc6eaa658dbc to your computer and use it in GitHub Desktop.
My top recommended Laravel packages
Package (in Alphabetical Order) Description
ARCANEDEV/LogViewer A nice and easy dashboard style interface for viewing Laravel logs
barryvdh/laravel-debugbar An amazing package for debugging and profiling your application via a handy GUI built into the dev stream of your application
barryvdh/laravel-ide-helper This is an excellent tool if using Laravel within an IDE (or VSCode with PHP extensions, like this one). It generates class maps for the application and instructs the IDE on how to analyse and traverse your Laravel application
BenSampo/laravel-enum A brilliant plugin that does exactly what it says, adds enums to Laravel. Very handy!
beyondcode/laravel-query-detector Excellent for catching any queries that may be presenting an N+1 scenario and throwing them in your face, with advice on how to fix them
enlightn/enlightn Really good for nailing down key Laravel performance issues, with analysis and tips on common issues
hoyvoy/laravel-cross-database-subqueries A mouth full, but does what it says. Laravel has a bug, I think its a bug, where it ignores the models connection definition when using subqueries when its perfectly capable of doing so and I think, is what is expected behavior
Jhnbrn90/laravel-package Okay, so not a package per-say, but it is an incredible resource on creating them
knuckleswtf/scribe Brilliant automated API docs generator, with Postman integration. Unfortunately, the original repo laravel-apidoc-generator appears to no longer be maintained , with one of the lead maintainers forking it to create Scribe! There is also a migration guide for this as part of the Scribe project
laravel/airlock or laravel/passport Both authentication layers for your application, for SPA's or just ways to easily integrate OAuth. Either way, well documented first-party plugins that are staple for these use cases
laravel/telescope Pretty much the defacto tool of choice for monitoring/debugging every part of Laravel in a dashboard fashion, via this first party package
lorisleiva/laravel-deployer A wrapper around deployer.org for Laravel, it allows easy access and customisation through Laravel's tool chain. It maps the relevant commands to artisan and places the deployer config within Laravel's for tidiness and scoping. Very handy for semi-autonomous and non-CI/CD deployments!
mad-web/laravel-initializer An excellent Laravel plugin that allows you to automate aspects of your Laravel environment, be it setting up a local environment from scratch or deploying to remote production environments
owen-it/laravel-auditing Need to track model data changes to provide an audit trail? This is the package for you!
rappasoft/laravel-authentication-log A quick and easy way to add logging to the Laravel Auth stack.
readme.so Not a Laravel package, just a really nice tool to make writing a project README more pleasant.
spatie/fork A very bare bones and simple process forking and async implementation. More can be found on the Stitcher blog article.
spatie/laravel-backup Amazing backup solution that runs within the scope of your app, to backup the project database and files
spatie/test-time Really handy Carbon wrapper for manipulate Carbon application wide during tests, making testing with variable dates much easier
StydeNet/enlighten Like Scribe above, but with more of an emphasis on documentation generation being automated. Looks like a pretty incredible bit of kit, and I cannot wait to try it!
symfony/symfony Again, not Laravel, technically. For those that don't know, Laravel is built on top of the Symfony framework, sharing a lot of its core. It's components are excellent and well documented, would highly recommend seeing if they have a utility class before you create one, they usually do! Saves re-inventing the wheel and keeps things maintainable
Wulfheart/pretty-routes Ever thought the routes command output is hard to read? Well, look no further! ... seriously.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment