Things to do after a fresh laravel install

Mohammed Samgan Khan

Application Security

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

When setting up a fresh Laravel installation, consider using the Laravel installer for a streamlined process, including selecting a starter kit such as Inertia/React or Livewire Volt with Class. Recommended packages for enhancing your Laravel setup include Laravel-error-solutions, laravel-schedule-monitor, laravel-env-keys-checker, and tighten/duster. Configuration tips include addressing the n+1 query problem and ensuring JSON responses for API routes in Laravel 11 and above. Example configurations for tlint, pint, and package.json are shared for better project setup.

This is very interesting but it would be nice to see the explanation as to why some of this should be done. No clue what tlint and pint are and why I should bother.
The N+1 solution is interesting but might be nice to know why/how it works and what the consequences of doing it are. We sometimes struggle with N+1 queries and a 1 line solution seems too good to be true without any regressions.

If there is package does not mean you have to use it, keep your technical debt low.

Install filament. And definently if there’s going to be an admin panel