Laravel Debugbar (Integrates PHP Debug Bar)

Overview

Laravel Debugbar

Unit Tests Packagist License Latest Stable Version Total Downloads

This is a package to integrate PHP Debug Bar with Laravel. It includes a ServiceProvider to register the debugbar and attach it to the output. You can publish assets and configure it through Laravel. It bootstraps some Collectors to work with Laravel and implements a couple custom DataCollectors, specific for Laravel. It is configured to display Redirects and (jQuery) Ajax Requests. (Shown in a dropdown) Read the documentation for more configuration options.

Debugbar 3.3 Screenshot

Note: Use the DebugBar only in development. It can slow the application down (because it has to gather data). So when experiencing slowness, try disabling some of the collectors.

This package includes some custom collectors:

  • QueryCollector: Show all queries, including binding + timing
  • RouteCollector: Show information about the current Route.
  • ViewCollector: Show the currently loaded views. (Optionally: display the shared data)
  • EventsCollector: Show all events
  • LaravelCollector: Show the Laravel version and Environment. (disabled by default)
  • SymfonyRequestCollector: replaces the RequestCollector with more information about the request/response
  • LogsCollector: Show the latest log entries from the storage logs. (disabled by default)
  • FilesCollector: Show the files that are included/required by PHP. (disabled by default)
  • ConfigCollector: Display the values from the config files. (disabled by default)
  • CacheCollector: Display all cache events. (disabled by default)

Bootstraps the following collectors for Laravel:

  • LogCollector: Show all Log messages
  • SwiftMailCollector and SwiftLogCollector for Mail

And the default collectors:

  • PhpInfoCollector
  • MessagesCollector
  • TimeDataCollector (With Booting and Application timing)
  • MemoryCollector
  • ExceptionsCollector

It also provides a facade interface (Debugbar) for easy logging Messages, Exceptions and Time

Installation

Require this package with composer. It is recommended to only require the package for development.

composer require barryvdh/laravel-debugbar --dev

Laravel uses Package Auto-Discovery, so doesn't require you to manually add the ServiceProvider.

The Debugbar will be enabled when APP_DEBUG is true.

If you use a catch-all/fallback route, make sure you load the Debugbar ServiceProvider before your own App ServiceProviders.

Laravel without auto-discovery:

If you don't use auto-discovery, add the ServiceProvider to the providers array in config/app.php

Barryvdh\Debugbar\ServiceProvider::class,

If you want to use the facade to log messages, add this to your facades in app.php:

'Debugbar' => Barryvdh\Debugbar\Facades\Debugbar::class,

The profiler is enabled by default, if you have APP_DEBUG=true. You can override that in the config (debugbar.enabled) or by setting DEBUGBAR_ENABLED in your .env. See more options in config/debugbar.php You can also set in your config if you want to include/exclude the vendor files also (FontAwesome, Highlight.js and jQuery). If you already use them in your site, set it to false. You can also only display the js or css vendors, by setting it to 'js' or 'css'. (Highlight.js requires both css + js, so set to true for syntax highlighting)

Copy the package config to your local config with the publish command:

php artisan vendor:publish --provider="Barryvdh\Debugbar\ServiceProvider"

Laravel with Octane:

Make sure to add LaravelDebugbar to your flush list in config/octane.php.

    'flush' => [
        \Barryvdh\Debugbar\LaravelDebugbar::class,
    ],

Lumen:

For Lumen, register a different Provider in bootstrap/app.php:

if (env('APP_DEBUG')) {
 $app->register(Barryvdh\Debugbar\LumenServiceProvider::class);
}

To change the configuration, copy the file to your config folder and enable it:

$app->configure('debugbar');

Usage

You can now add messages using the Facade (when added), using the PSR-3 levels (debug, info, notice, warning, error, critical, alert, emergency):

Debugbar::info($object);
Debugbar::error('Error!');
Debugbar::warning('Watch out…');
Debugbar::addMessage('Another message', 'mylabel');

And start/stop timing:

Debugbar::startMeasure('render','Time for rendering');
Debugbar::stopMeasure('render');
Debugbar::addMeasure('now', LARAVEL_START, microtime(true));
Debugbar::measure('My long operation', function() {
    // Do something…
});

Or log exceptions:

try {
    throw new Exception('foobar');
} catch (Exception $e) {
    Debugbar::addThrowable($e);
}

There are also helper functions available for the most common calls:

// All arguments will be dumped as a debug message
debug($var1, $someString, $intValue, $object);

// `$collection->debug()` will return the collection and dump it as a debug message. Like `$collection->dump()`
collect([$var1, $someString])->debug();

start_measure('render','Time for rendering');
stop_measure('render');
add_measure('now', LARAVEL_START, microtime(true));
measure('My long operation', function() {
    // Do something…
});

If you want you can add your own DataCollectors, through the Container or the Facade:

Debugbar::addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));
//Or via the App container:
$debugbar = App::make('debugbar');
$debugbar->addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));

By default, the Debugbar is injected just before </body>. If you want to inject the Debugbar yourself, set the config option 'inject' to false and use the renderer yourself and follow http://phpdebugbar.com/docs/rendering.html

$renderer = Debugbar::getJavascriptRenderer();

Note: Not using the auto-inject, will disable the Request information, because that is added After the response. You can add the default_request datacollector in the config as alternative.

Enabling/Disabling on run time

You can enable or disable the debugbar during run time.

\Debugbar::enable();
\Debugbar::disable();

NB. Once enabled, the collectors are added (and could produce extra overhead), so if you want to use the debugbar in production, disable in the config and only enable when needed.

Twig Integration

Laravel Debugbar comes with two Twig Extensions. These are tested with rcrowe/TwigBridge 0.6.x

Add the following extensions to your TwigBridge config/extensions.php (or register the extensions manually)

'Barryvdh\Debugbar\Twig\Extension\Debug',
'Barryvdh\Debugbar\Twig\Extension\Dump',
'Barryvdh\Debugbar\Twig\Extension\Stopwatch',

The Dump extension will replace the dump function to output variables using the DataFormatter. The Debug extension adds a debug() function which passes variables to the Message Collector, instead of showing it directly in the template. It dumps the arguments, or when empty; all context variables.

{{ debug() }}
{{ debug(user, categories) }}

The Stopwatch extension adds a stopwatch tag similar to the one in Symfony/Silex Twigbridge.

{% stopwatch "foo" %}
    …some things that gets timed
{% endstopwatch %}
Comments
  • PhpDebugBar is not defined - Laravel 5.1

    PhpDebugBar is not defined - Laravel 5.1

    Hi, I know that a similar issue has been solved before, but I tried to follow the same suggested procedures but none of them worked for me. I'm using Laravel 5.1 .

    I'm getting the following 404 not found errors :

    <http://my_website_url/_debugbar/assets/stylesheets?1436453519> <http://my_website_url/_debugbar/assets/javascript?1423122680>

    and <PhpDebugBar is not defined>

    I put debugbar first in the ServiceProviders and I don't have a catchall in my routes. The only thing I have in my routes is the following: <Route::get('/', 'WelcomeController@index');>

    opened by omaromran 47
  • Refused to get unsafe header

    Refused to get unsafe header "phpdebugbar"

    Hi,

    I'm currently in Chrome latest version (just checked it)

    As of this morning I'm getting two error in my console.

    • Refused to get unsafe header "phpdebugbar-id"
    • Refused to get unsafe header "phpdebugbar"

    I'm thinking this is not a specific debugbar notification so I tried Googling for it but no luck.

    I disabled the debugbar for testing purposes which results in no errors at all (obviously).

    Does anyone have a clue wat is going on?

    stale 
    opened by boywijnmaalen 47
  • assets.css and assets.js not found

    assets.css and assets.js not found

    Hi, I just updated to the latest laravel-debugbar and now I'm getting 404 Not Found errors when loading

    /_debugbar/assets.css?xxxxx /_debugbar/assets.js?xxxxx

    I can see that the routes are properly registered, but for some reason Nginx is not routing it correct. Could it be my Nginx config? Here is my config taken from the Server section below:

        location / {
    
            # URLs to attempt, including pretty ones.
            try_files   $uri $uri/ /index.php?$query_string;
    
        }
    
        # Remove trailing slash to please routing system.
        if (!-d $request_filename) {
            rewrite     ^/(.+)/$ /$1 permanent;
        }
    
        # PHP FPM configuration.
        location ~ \.php$ {
                fastcgi_pass                    unix:/var/run/php-fcgi.sock;
                fastcgi_index                   index.php;
                fastcgi_split_path_info         ^(.+\.php)(/.+)$;
                include                         /etc/nginx/fcgi.conf;
                fastcgi_param                   SCRIPT_FILENAME $document_root$fastcgi_script_name;
        }
    
        # We don't need .ht files with nginx.
        location ~ /\.ht {
                deny all;
        }
    
        # Set header expirations on per-project basis
        location ~* \.(?:ico|css|js|jpe?g|JPG|png|svg|woff)$ {
                expires 365d;
    
        }
    
    opened by anthonywkchan 36
  • REST API profiling

    REST API profiling

    Hi! I'm having an API built with laravel. And I need to do some profiling on it. It's the classic REST API that returns json. How can I profile it with debugbar?

    stale 
    opened by qstyler 35
  • debugbar refreshes on each ajax call

    debugbar refreshes on each ajax call

    Hi,

    Our codebase has a heartbeat ajax call every X seconds. So we're doing quite some ajax call to be honest. (it is planned to move this to a socket, but we'll need to schedule that for next year probably)

    Anyway. On my local machine, I can easily click the "folder icon" in my laravel debugbar, and select which call I would like to see the details for. It works great. The same code deployed on an AWS instance however, automatically always updates my debugbar view to the latest ajax call which is pretty annoying, because it updates everything every X seconds, and I don't have time to check the queries for a specific call or whatever.

    Has anyone experienced this issue and/or found a solution? I have googled and searched the issues on here, but to no avail.

    Thanks very much!

    stale 
    opened by denjaland 33
  • Notice: Trying to get property 'cookies' of non-object

    Notice: Trying to get property 'cookies' of non-object

    Debugbar: 3.2.8 Laravel: 5.7 and 5.8 and 6

    Debugbar is causing cookie/session problems when being injected via InjectDebugbar() on error pages.

    ErrorException/public/index.php in ? Notice: Trying to get property 'cookies' of non-object

    This occurs whenever a 404 error/page is returned. the 404 page is displayed, the debugbar is missing from it and our error tracking system reports this error.

    • Install Laravel
    • Install Debugbar
    • Install something like Sentry.io to track the errors
    • Navigate to a non-existent route
    • You'll get a 404, but with no debugbar
    • and Sentry.io will show a error of "Notice: Trying to get property 'cookies' of non-object"
    ErrorException: Notice: Trying to get property 'cookies' of non-object
    #35 /vendor/laravel/framework/src/Illuminate/Session/CookieSessionHandler.php(69): Illuminate\Session\CookieSessionHandler::read
    #34 /vendor/laravel/framework/src/Illuminate/Session/Store.php(97): Illuminate\Session\Store::readFromHandler
    #33 /vendor/laravel/framework/src/Illuminate/Session/Store.php(87): Illuminate\Session\Store::loadSession
    #32 /vendor/laravel/framework/src/Illuminate/Session/Store.php(71): Illuminate\Session\Store::start
    #31 /vendor/laravel/framework/src/Illuminate/Support/Manager.php(146): Illuminate\Support\Manager::__call
    #30 /vendor/barryvdh/laravel-debugbar/src/SymfonyHttpDriver.php(42): Barryvdh\Debugbar\SymfonyHttpDriver::isSessionStarted
    #29 /vendor/maximebf/debugbar/src/DebugBar/DebugBar.php(446): DebugBar\DebugBar::initStackSession
    #28 /vendor/maximebf/debugbar/src/DebugBar/DebugBar.php(359): DebugBar\DebugBar::hasStackedData
    #27 /vendor/maximebf/debugbar/src/DebugBar/JavascriptRenderer.php(984): DebugBar\JavascriptRenderer::render
    #26 /vendor/barryvdh/laravel-debugbar/src/LaravelDebugbar.php(862): Barryvdh\Debugbar\LaravelDebugbar::injectDebugbar
    #25 /vendor/barryvdh/laravel-debugbar/src/LaravelDebugbar.php(747): Barryvdh\Debugbar\LaravelDebugbar::modifyResponse
    #24 /vendor/barryvdh/laravel-debugbar/src/Middleware/InjectDebugbar.php(74): Barryvdh\Debugbar\Middleware\InjectDebugbar::handle
    #23 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\Pipeline\Pipeline::Illuminate\Pipeline\{closure}
    #22 /vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Pipeline::Illuminate\Routing\{closure}
    #21 /vendor/fideloper/proxy/src/TrustProxies.php(57): Fideloper\Proxy\TrustProxies::handle
    #20 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\Pipeline\Pipeline::Illuminate\Pipeline\{closure}
    #19 /vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Pipeline::Illuminate\Routing\{closure}
    #18 /vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\Foundation\Http\Middleware\TransformsRequest::handle
    #17 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\Pipeline\Pipeline::Illuminate\Pipeline\{closure}
    #16 /vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Pipeline::Illuminate\Routing\{closure}
    #15 /vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\Foundation\Http\Middleware\TransformsRequest::handle
    #14 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\Pipeline\Pipeline::Illuminate\Pipeline\{closure}
    #13 /vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Pipeline::Illuminate\Routing\{closure}
    #12 /vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Foundation\Http\Middleware\ValidatePostSize::handle
    #11 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\Pipeline\Pipeline::Illuminate\Pipeline\{closure}
    #10 /vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Pipeline::Illuminate\Routing\{closure}
    #9 /vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(62): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::handle
    #8 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\Pipeline\Pipeline::Illuminate\Pipeline\{closure}
    #7 /vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Pipeline::Illuminate\Routing\{closure}
    #6 /vendor/barryvdh/laravel-cors/src/HandlePreflight.php(29): Barryvdh\Cors\HandlePreflight::handle
    #5 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\Pipeline\Pipeline::Illuminate\Pipeline\{closure}
    #4 /vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Pipeline::Illuminate\Routing\{closure}
    #3 /vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\Pipeline\Pipeline::then
    #2 /vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(151): Illuminate\Foundation\Http\Kernel::sendRequestThroughRouter
    #1 /vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel::handle
    #0 /public/index.php(53): null
    
    stale 
    opened by SlyDave 32
  • Debugbar::enable() does not seem to work!

    Debugbar::enable() does not seem to work!

    I have the below code in a middleware and disabling debug_bar (if i have it enabled by default) works fine! However if I try the opposite, meaning having the debug bar disabled by default and try to enable it on demand then id does not work.

    Any ideas?

    P.S. lavavel's own debug mode works fine like this! gets enable or disabled when i want!

        if ($request->has('disable_debug')) {
            \Config::set('app.debug', false);
            \Debugbar::disable();
        }
        if ($request->has('enable_debug')) {
            \Config::set('app.debug', true);
            \Debugbar::enable();
        }
    
    stale 
    opened by unitedworx 29
  • Debugbar is not displaying in Laravel 5

    Debugbar is not displaying in Laravel 5

    I thought this was a Laravel 5.0.16 issue, however I've tested with a fresh install of 5.0.1 with the same results as below. I have a few projects created I believe with 5.0.12, where the debugbar was working. They have been updated to 5.0.16 and still display the debugbar. However new projects are not showing the debugbar.

    Testing with a fresh install of Laravel 5.0.16 composer create-project laravel/laravel --prefer-dist composer require barryvdh/laravel-debugbar

    Added to config/app.php 'Barryvdh\Debugbar\ServiceProvider', 'Debugbar' => 'Barryvdh\Debugbar\Facade',

    php artisan vendor:publish successfully creates config/debugbar.php

    stat -c %a storage/ returns 777

    .env APP_ENV=local APP_DEBUG=true

    The Laravel 5 welcome screen is displayed, however the debugbar is not. Checking view source shows that the debugbar code has been added to the page. The following assets return a 404. /_debugbar/assets/stylesheets?1426726547 /_debugbar/assets/javascript?1426726547

    opened by Daem0nX 29
  • Debugbar Not Showing

    Debugbar Not Showing

    Issue Type

    • [x] Bug Report

    End User Info

    -- Laravel Version: 5.6.38

    -- PHP Version: 7.2.10

    -- Database Driver & Version: MariaDB 10.3.8

    -- Web Server Driver & Version: NGINX 1.15.0

    -- OS Driver and Version: Ubuntu 18.04.1

    Issue:

    • Installed using composer require barryvdh/laravel-debugbar
    • Published config using php artisan vendor:publish --provider="Barryvdh\Debugbar\ServiceProvider"
    • Set .env APP_ENV=local APP_DEBUG=true
    • Set debugbar.php config enabled to true
    • Ran php artisan clear:all Clearing several common cache's ... Blade templates cached successfully! Route cache cleared! Routes cached successfully! Configuration cache cleared!
    • Cleared OPCache php artisan opcache:clear Opcode cache cleared

    I don't see debug bar in bottom of browser...

    opened by HDVinnie 26
  • Unable to view AJAX requests results

    Unable to view AJAX requests results

    Hi,

    I'm unable to get AJAX queries to properly report on 1.8.3.

    I have the following settings of interest in my config.php

    'include_vendors' => false,
    'capture_ajax' => true,
    

    Some information that is probably of interest to debugging this issue:

    • Provided jquery is 1.11.0
    • The request returns a phpdebugbar-id in the response header
    • A breakpoint in the bindToXHR method of the extended AjaxHandler.prototype will only trigger on setup. XMLHttpRequest.prototype.open never appears to be called when $.ajax is called (by a third-party library).
    • Browser is chrome 39.0.2171.95 (64-bit)

    The application using laravel-debugbar also makes use of angular, for which we use the ng-phpdebugbar module in order to track $http requests. This works properly. I've also verified that it doesn't interfere with php-debugbar by disabling it completely.

    Let me know if any other information might be useful to debug this.

    Thanks!

    opened by tomzx 25
  • Tabs not working.

    Tabs not working.

    I started a new project with Laravel Debugbar and the tabs are not expanding up they act like there going to but don't. I've been using this for a while now and I've never had this problem till now. Thanks for any help.

    opened by dragonfire1119 24
  • feat: json_encode context with JSON_PRETTY_PRINT flag

    feat: json_encode context with JSON_PRETTY_PRINT flag

    This commit is intended for the improvement in the readability of messages if they have long context data.

    For example, without pretty print image

    With pretty print image

    opened by huzaifaarain 0
  • Feature: add an option to disable deprecation warnings, or set a custom error_reporting level

    Feature: add an option to disable deprecation warnings, or set a custom error_reporting level

    Hello all,

    I've got a feature request to suggest: add an option to disable deprecation warnings, or set a custom error_reporting level.

    This is expecially useful for new PHP 8.2 projects where the codebase is heavily using Dynamic Properties.

    I couldn't find anywhere else such an option: i've had a look at the source code to see how the option error_handler is used, but the only thing it does is to set the error handler to LaravelDebugBar::handleError():

    File: vendor/barryvdh/laravel-debugbar/src/LaravelDebugbar.php

    Source:

    // Set custom error handler
    if ($app['config']->get('debugbar.error_handler', false)) {
            set_error_handler([$this, 'handleError']);
    }
    

    I think it should become:

    // Set custom error handler
    if ($app['config']->get('debugbar.error_handler', false)) {
            // get the error_level config
            $level = $app['config']->get('debugbar.error_level', E_ALL);
            
            // call our handleError with $level
            set_error_handler([$this, 'handleError'], $level);
    }
    

    Side note: I've modified my codebase using #[AllowDynamicProperties] on all classes using Dynamic Properties as suggested on deprecate_dynamic_properties RFC. Debugbar still catch this errors. Also tried to error_reporting(E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED); on AppProvider, but with no success.

    opened by mauriziofonte 0
  • Feature: allow collectors to be overridden for custom changes

    Feature: allow collectors to be overridden for custom changes

    As the title says. As the collectors are used directly there is no way to easily override them when you need to make some changes to the original collectors. Would be great if they would use the native laravel bind methods to be able to override them.

    opened by TivoSoho 0
  • Feature: sort DB queries alphabetically

    Feature: sort DB queries alphabetically

    I love debugging queries with the debugbar, however one issue is that we may have certain queries repeat. It would be immensely helpful if we could have an action to sort them at least alphabetically in the frontend so that we can more easily detect duplicated queries. Sorting by time is also helpful to detect slower queries per page.

    I know a feature request with an open PR was done, but that was back in 2019. Not sure if it can be applied.

    opened by TivoSoho 0
  • fix: deprecated dynamic property on PHP 8.2

    fix: deprecated dynamic property on PHP 8.2

    Fixing deprecated on PHP 8.2 :

    • Creation of dynamic property Barryvdh\Debugbar\DataFormatter\QueryFormatter::$cloner is deprecated
    • Creation of dynamic property Barryvdh\Debugbar\DataFormatter\QueryFormatter::$dumper is deprecated
    • Creation of dynamic property Barryvdh\Debugbar\DataFormatter\SimpleFormatter::$cloner is deprecated
    • Creation of dynamic property Barryvdh\Debugbar\DataFormatter\SimpleFormatter::$dumper is deprecated

    Reference : https://php.watch/versions/8.2/dynamic-properties-deprecated

    opened by aldok10 0
  • Non-string messages not rendering when exception raised

    Non-string messages not rendering when exception raised

    • Laravel v9.44.0 (PHP v8.1.13)
    • barryvdh/laravel-debugbar version - v3.7.0

    How to reproduce

    Modify the laravel example app by inserting the following lines anywhere into resources/views/welcome.blade.php:

    @php
    $arr = [
        'name' => 'John',
        'age' => 30,
        'cars' => [
            'Ford',
            'BMW',
            'Toyota'
        ]
    ];
    \Debugbar::log($arr);
    
    throw new Exception('Error Processing Request', 1);
    
    @endphp
    

    Observed behavior

    image

    Expected behavior

    With the throw new Exception('Error Processing Request', 1); line removed / commented out: image

    opened by michprev 0
Releases(v3.7.0)
Owner
Barry vd. Heuvel
Barry vd. Heuvel
Integrates the Trix Editor with Laravel. Inspired by the Action Text gem from Rails.

Integrates the Trix Editor with Laravel. Inspired by the Action Text gem from Rails. Installation You can install the package via composer: composer r

Tony Messias 267 Jan 4, 2023
Integrates libphonenumber into your Symfony application

PhoneNumberBundle This bundle is a fork of misd-service-development/phone-number-bundle. As this project doesn't look maintained anymore, we decided t

Olivier Dolbeau 161 Dec 23, 2022
List of 77 languages for Laravel Framework 4, 5, 6, 7 and 8, Laravel Jetstream , Laravel Fortify, Laravel Breeze, Laravel Cashier, Laravel Nova and Laravel Spark.

Laravel Lang In this repository, you can find the lang files for the Laravel Framework 4/5/6/7/8, Laravel Jetstream , Laravel Fortify, Laravel Cashier

Laravel Lang 6.9k Jan 2, 2023
⚡ Laravel Charts — Build charts using laravel. The laravel adapter for Chartisan.

What is laravel charts? Charts is a Laravel library used to create Charts using Chartisan. Chartisan does already have a PHP adapter. However, this li

Erik C. Forés 31 Dec 18, 2022
Laravel Kickstart is a Laravel starter configuration that helps you build Laravel websites faster.

Laravel Kickstart What is Laravel Kickstart? Laravel Kickstart is a Laravel starter configuration that helps you build Laravel websites faster. It com

Sam Rapaport 46 Oct 1, 2022
Laravel User Activity Log - a package for Laravel 8.x that provides easy to use features to log the activities of the users of your Laravel app

Laravel User Activity Log - a package for Laravel 8.x that provides easy to use features to log the activities of the users of your Laravel app

null 9 Dec 14, 2022
laravel - Potion is a pure PHP asset manager for Laravel 5 based off of Assetic.

laravel-potion Potion is a pure PHP asset manager for Laravel based off of Assetic. Description Laravel 5 comes with a great asset manager called Elix

Matthew R. Miller 61 Mar 1, 2022
Laravel mercado pago es un paquete que te ayuda a implementar el sdk de mercado pago para php en laravel

Introducción Laravel mercado pago es un paquete que te ayuda a implementar el sdk de mercado pago para php en laravel. ?? Instalación Para instalar ut

null 7 Sep 23, 2022
Laravel breeze is a PHP Laravel library that provides Authentication features such as Login page , Register, Reset Password and creating all Sessions Required.

About Laravel breeze To give you a head start building your new Laravel application, we are happy to offer authentication and application starter kits

null 3 Jul 30, 2022
Laravel 4.* and 5.* service providers to handle PHP errors, dump variables, execute PHP code remotely in Google Chrome

Laravel 4.* service provider for PHP Console See https://github.com/barbushin/php-console-laravel/releases/tag/1.2.1 Use "php-console/laravel-service-

Sergey 73 Jun 1, 2022
Laravel Segment is an opinionated, approach to integrating Segment into your Laravel application.

Laravel Segment Laravel Segment is an opinionated, approach to integrating Segment into your Laravel application. Installation You can install the pac

Octohook 13 May 16, 2022
Laravel Sanctum support for Laravel Lighthouse

Lighthouse Sanctum Add Laravel Sanctum support to Lighthouse Requirements Installation Usage Login Logout Register Email Verification Forgot Password

Daniël de Wit 43 Dec 21, 2022
Bring Laravel 8's cursor pagination to Laravel 6, 7

Laravel Cursor Paginate for laravel 6,7 Installation You can install the package via composer: composer require vanthao03596/laravel-cursor-paginate U

Pham Thao 9 Nov 10, 2022
A package that uses blade templates to control how markdown is converted to HTML inside Laravel, as well as providing support for markdown files to Laravel views.

Install Install via composer. $ composer require olliecodes/laravel-etched-blade Once installed you'll want to publish the config. $ php artisan vendo

Ollie Codes 19 Jul 5, 2021
A light weight laravel package that facilitates dealing with arabic concepts using a set of classes and methods to make laravel speaks arabic

A light weight laravel package that facilitates dealing with arabic concepts using a set of classes and methods to make laravel speaks arabic! concepts like , Hijri Dates & Arabic strings and so on ..

Adnane Kadri 49 Jun 22, 2022
Jetstrap is a lightweight laravel 8 package that focuses on the VIEW side of Jetstream / Breeze package installed in your Laravel application

A Laravel 8 package to easily switch TailwindCSS resources generated by Laravel Jetstream and Breeze to Bootstrap 4.

null 686 Dec 28, 2022
Laravel Jetstream is a beautifully designed application scaffolding for Laravel.

Laravel Jetstream is a beautifully designed application scaffolding for Laravel. Jetstream provides the perfect starting point for your next Laravel application and includes login, registration, email verification, two-factor authentication, session management, API support via Laravel Sanctum, and optional team management.

The Laravel Framework 3.5k Jan 8, 2023
Laravel Larex lets you translate your whole Laravel application from a single CSV file.

Laravel Larex Translate Laravel Apps from a CSV File Laravel Larex lets you translate your whole Laravel application from a single CSV file. You can i

Luca Patera 68 Dec 12, 2022
A Laravel package that adds a simple image functionality to any Laravel model

Laraimage A Laravel package that adds a simple image functionality to any Laravel model Introduction Laraimage served four use cases when using images

Hussein Feras 52 Jul 17, 2022