by Devin Yang
(This article was automatically translated.)

Published - 8 years ago ( Updated - 8 years ago )

What packages do you definitely have installed on your Laravel application?
There are four-star kits here, almost everyone will install them,
Let's take a look at my usage experience.

Here's what I've tried:

1. Laravel Debugbar.

It is OK after trying it out, you can decide whether to use this function through APP_DEBUG in env.
When I use it in development mode, my favorite is probably his Views,
Because I loaded a lot of Blade templates in my self-built background,
When I need to adjust, it is easy to recall which template I want to adjust, and it may take a long time to change it.
Laravel debug bar

2. Laravel IDE Helper

If there is PhpStorm, I think this must be installed.
The IDE can't read it without installing it.
Before PhpStorm did not use laravel-ide-help
After installation, Route displays, and there is no bottom line for marking errors.
PhpStorm not using laravel-ide-help after

Download and drop it into the project directory: (L5)
_ide_helper.php
This file does not require version control,
Remember that you can modify the .gitignore file in the Laravel Project directory, add _ide_helper.php , and ignore it.

Here is a Laracasts video installation tutorial: https://laracasts.com/series/how-to-be-awesome-in-phpstorm/episodes/15

3. Laravel Collective HTML

Since my background form is fully controllable form template, repeated use,
All modified values ​​will be automatically substituted into the input or automatically selected from the dropdown.
This is not attractive to me, Blade is really the best prototype engine I have seen so far.


There are more useful packages, you can refer to the source of the original text:
https://mattstauffer.co/blog/what-packages-do-you-install-on-every-laravel-application-you-create

Tags: Laravel Packages

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


docker,dlaravel

D-Laravel 1.5.5 Change Notes

D-Laravel's fpm image was rebuilt using the official dockerfile of docker php before php 7.2.1. And so I can specify that the default owner of fpm is dlaravel, --with-fpm-user=USER Set the user for php-fpm to run as. (default: nobody) --with-fpm-group=GRP Set the group for php-fpm to run as.

dlaravel

D-Laravel's sublime plug-in can be installed by Package Control.

Mac or Linux users can now install the D-Laravel alias package from Sublime3's package control. Through D-Laravel alias, we can execute artisan and composer commands in the container in an easier way. In the docker environment, do you want to use composer to install the package? You don’t need to enter the container, or set the ce alias of composer, and you can execute it directly in sublime.

laravel, livewire

livewire important notes

Before starting your Livewire journey, here are three basic considerations about public properties: 1. The property name must not conflict with a property name reserved for Livewire (such as $rules or $message) 2. Store in Data in public properties is visible to front-end JavaScript. Therefore, you should not store sensitive data in it. 3. Properties can only be JavaScript-friendly data types (string, integer, array, boolean), or one of the following PHP types: Stringable, Collection, DateTime, Model, EloquentCollection.