Laravel 5.5 Woops is back, let's check it out.

by Devin Yang
(This article was automatically translated.)

Published - 7 years ago ( Updated - 7 years ago )

Whoops is a nice little library that helps you better develop and maintain your projects, helping you handle errors and exceptions in a less painful way.
, it was preloaded in Laravel 4, but it was removed in Laravel 5.0, and now 5.5 is back....

Some features of Whoops include:

- Flexible, stack-based error handling
- No dependencies are required to use the current stand-alone library
- Simple API for handling exceptions, tracking frames and their data
-Include a stunning error page within your web application
- Includes the ability to open referenced files directly in editors and IDEs
- Includes handlers for different response formats (JSON, XML, SOAP)
-Easy to extend and integrate with existing libraries
- Clean, well-structured and proven codebase

Tags: laravel woops

Devin Yang

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

No Comment

Post your comment

Login is required to leave comments

laravel docker

About D-Laravel's project mode

If you are a new user, I suggest you use my latest environment phpenv instead. https://github.com/DevinY/phpenv

d-laravel,docker

D-Laravel v1.2.1 version change description (recommended update, must avoid stepping on thunder)

D-Laravel v1.2.1 revision instructions use GuzzleHttp\Client; When posting, there is an access denied problem. If you are upgrading from an older version, you may need to adjust the configuration file in etc/default-ssl.conf (if there is one) Please adjust php:9000 to web:9000, you can adjust it by executing ./console secure once. In the docker-compose configuration file, change the PHP-FPM container to network_mode: "service:web"...

Laravel,artisan

About the operation of --env in Laravel's artisan

This article uses Laravel 9.40.1 for operation. I believe many people know the usage of --env, but I still provide some information for Laravel beginners. In the artisan command, we can use --env to specify different .env files, so that under different subdomains, I can use different environments or even different databases. You should have also noticed that this site uses a multilingual environment, do you write two sets? Of course not, basically I created multiple .env in the same Project.