[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-8118":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":25,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":32,"readmeContent":33,"aiSummary":34,"trendingCount":16,"starSnapshotCount":16,"syncStatus":35,"lastSyncTime":36,"discoverSource":37},8118,"laravel-debugbar","fruitcake\u002Flaravel-debugbar","fruitcake","Debugbar for Laravel (Integrates PHP Debug Bar)","http:\u002F\u002Flaraveldebugbar.com\u002F",null,"PHP",19234,1606,273,73,0,1,5,40,6,44.62,"MIT License",false,"master",true,[27,28,29,30,31],"debugbar","developer-tool","laravel","profiler","toolbar","2026-06-12 02:01:49","## Debugbar for Laravel\n\n![Unit Tests](https:\u002F\u002Fgithub.com\u002Ffruitcake\u002Flaravel-debugbar\u002Fworkflows\u002FUnit%20Tests\u002Fbadge.svg)\n[![Packagist License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicence-MIT-blue)](https:\u002F\u002Fchoosealicense.com\u002Flicenses\u002Fmit)\n[![Latest Stable Version](https:\u002F\u002Fimg.shields.io\u002Fpackagist\u002Fv\u002Ffruitcake\u002Flaravel-debugbar?label=Stable)](https:\u002F\u002Fpackagist.org\u002Fpackages\u002Ffruitcake\u002Flaravel-debugbar)\n[![Total Downloads](https:\u002F\u002Fimg.shields.io\u002Fpackagist\u002Fdt\u002Fbarryvdh\u002Flaravel-debugbar?label=Downloads)](https:\u002F\u002Fpackagist.org\u002Fpackages\u002Ffruitcake\u002Flaravel-debugbar)\n[![Fruitcake](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FPowered%20By-Fruitcake-b2bc35.svg)](https:\u002F\u002Ffruitcake.nl)\n\nThis is a package to integrate [PHP Debug Bar](https:\u002F\u002Fgithub.com\u002Fphp-debugbar\u002Fphp-debugbar) with Laravel.\nIt includes a ServiceProvider to register the debugbar and attach it to the output. You can publish assets and configure it through Laravel.\nIt bootstraps some Collectors to work with Laravel and implements a couple custom DataCollectors, specific for Laravel.\nIt is configured to display Redirects and Ajax\u002FLivewire Requests, which are shown in a dropdown.\nRead the [documentation](https:\u002F\u002Fphp-debugbar.com\u002Fdocs) for more configuration options.\n\n![Debugbar Dark Mode screenshot](https:\u002F\u002Fgithub.com\u002Ffruitcake\u002Flaravel-debugbar\u002Fassets\u002F973269\u002F6600837a-8b2d-4acb-ab0c-158c9ca5439c)\n\n> [!CAUTION]\n> Use the DebugBar only in development. Do not use Debugbar on publicly accessible websites, as it will leak information from stored requests (by design).\n\n> [!WARNING]\n> It can also slow the application down (because it has to gather and render data). So when experiencing slowness, try disabling some of the collectors.\n\nThis package includes some custom collectors:\n\n- QueryCollector: Show all queries, including binding + timing\n- RouteCollector: Show information about the current Route.\n- ViewCollector: Show the currently loaded views. (Optionally: display the shared data)\n- EventsCollector: Show all events\n- LaravelCollector: Show the Laravel version and Environment. (disabled by default)\n- SymfonyRequestCollector: replaces the RequestCollector with more information about the request\u002Fresponse\n- LogsCollector: Show the latest log entries from the storage logs. (disabled by default)\n- FilesCollector: Show the files that are included\u002Frequired by PHP. (disabled by default)\n- ConfigCollector: Display the values from the config files. (disabled by default)\n- CacheCollector: Display all cache events. (disabled by default)\n\nBootstraps the following collectors for Laravel:\n\n- LogCollector: Show all Log messages\n- SymfonyMailCollector for Mail\n\nAnd the default collectors:\n\n- PhpInfoCollector\n- MessagesCollector\n- TimeDataCollector (With Booting and Application timing)\n- MemoryCollector\n- ExceptionsCollector\n\nIt also provides a facade interface (`Debugbar`) for easy logging Messages, Exceptions and Time\n\n## Installation\n\nRequire this package with composer. It is recommended to only require the package for development.\n\n```shell\ncomposer require fruitcake\u002Flaravel-debugbar --dev\n```\n\n> Note: The package name has changed to `fruitcake\u002Flaravel-debugbar`. If you're using `barryvdh\u002Flaravel-debugbar`,\n> you can safely replace this with the new package name: `composer remove barryvdh\u002Flaravel-debugbar --dev --no-scripts`\n\nLaravel uses Package Auto-Discovery, so doesn't require you to manually add the ServiceProvider.\n\nThe Debugbar will be enabled when `APP_DEBUG` is `true` and when the environment is not `production` or `testing`.\n\nYou can disable it in the config (`debugbar.enabled`) or by setting `DEBUGBAR_ENABLED` in your `.env`. See more options in `config\u002Fdebugbar.php`\nYou can also set in your config if you want to include\u002Fexclude the vendor files also (FontAwesome, Highlight.js and jQuery). If you already use them in your site, set it to false.\nYou 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)\n\n#### Copy the package config to your local config with the publish command:\n\n```shell\nphp artisan vendor:publish --provider='Fruitcake\\LaravelDebugbar\\ServiceProvider'\n```\n\n### Laravel with Octane:\n\nLaravel Debugbar 4.x works out of the box with Octane. No need to add anything to your config.\n\nIf you're upgrading from Laravel Debugbar 3.x, remove the 'flush' config for Debugbar in `config\u002Foctane.php`.\n\n## Usage\n\nYou can now add messages using the Facade (when added), using the PSR-3 levels (debug, info, notice, warning, error, critical, alert, emergency):\n\n```php\nDebugbar::info($object);\nDebugbar::error('Error!');\nDebugbar::warning('Watch out…');\nDebugbar::addMessage('Another message', 'mylabel');\n```\n\nAnd start\u002Fstop timing:\n\n```php\nDebugbar::startMeasure('render','Time for rendering');\nDebugbar::stopMeasure('render');\nDebugbar::addMeasure('now', LARAVEL_START, microtime(true));\nDebugbar::measure('My long operation', function() {\n    \u002F\u002F Do something…\n});\n```\n\nOr log exceptions:\n\n```php\ntry {\n    throw new Exception('foobar');\n} catch (Exception $e) {\n    Debugbar::addThrowable($e);\n}\n```\n\nThere are also helper functions available for the most common calls:\n\n```php\n\u002F\u002F All arguments will be dumped as a debug message\ndebug($var1, $someString, $intValue, $object);\n\n\u002F\u002F `$collection->debug()` will return the collection and dump it as a debug message. Like `$collection->dump()`\ncollect([$var1, $someString])->debug();\n\nstart_measure('render','Time for rendering');\nstop_measure('render');\nadd_measure('now', LARAVEL_START, microtime(true));\nmeasure('My long operation', function() {\n    \u002F\u002F Do something…\n});\n```\n\nIf you want you can add your own DataCollectors, through the Container or the Facade:\n\n```php\nDebugbar::addCollector(new DebugBar\\DataCollector\\MessagesCollector('my_messages'));\n\u002F\u002F Or via the App container:\n$debugbar = App::make('debugbar');\n$debugbar->addCollector(new DebugBar\\DataCollector\\MessagesCollector('my_messages'));\n```\n\nBy default, the Debugbar is injected just before `\u003C\u002Fbody>`. If you want to inject the Debugbar yourself,\nset the config option 'inject' to false and use the renderer yourself and follow https:\u002F\u002Fphp-debugbar.com\u002Fdocs\u002Frendering\n\n```php\n$renderer = Debugbar::getJavascriptRenderer();\n```\n\nNote: Not using the auto-inject, will disable the Request information, because that is added After the response.\nYou can add the default_request datacollector in the config as alternative.\n\n## Enabling\u002FDisabling on run time\n\nYou can enable or disable the debugbar during run time.\n\n```php\n\\Debugbar::enable();\n\\Debugbar::disable();\n```\n\nNB. 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.\n\n> Note: by default Debugbar can only be enabled in debug mode and non-production environments. It's highly recommended to don't install this in production at all.\n> If you really need to enable it in production, you can set `debugbar.force_allow_enable` to true, or set `DEBUGBAR_FORCE_ALLOW_ENABLE=true` in your .env.\n> This will not enable the Debugbar, but will run the ServiceProvider bootstrap so you can enable it after booting.\n\n## Storage\n\nDebugbar remembers previous requests, which you can view using the Browse button on the right. This will only work if you enable `debugbar.storage.open` in the config.\nMake sure you only do this on local development, because otherwise other people will be able to view previous requests.\nIn general, Debugbar should only be used locally or at least restricted by IP.\nIt's possible to pass a callback, which will receive the Request object, so you can determine access to the OpenHandler storage.\n\n## Twig Integration\n\nLaravel Debugbar comes with two Twig Extensions. These are tested with [rcrowe\u002FTwigBridge](https:\u002F\u002Fgithub.com\u002Frcrowe\u002FTwigBridge) 0.6.x\n\nAdd the following extensions to your TwigBridge config\u002Fextensions.php (or register the extensions manually)\n\n```php\n'Fruitcake\\LaravelDebugbar\\Twig\\Extension\\Debug',\n'Fruitcake\\LaravelDebugbar\\Twig\\Extension\\Dump',\n'Fruitcake\\LaravelDebugbar\\Twig\\Extension\\Stopwatch',\n```\n\nThe Dump extension will replace the [dump function](https:\u002F\u002Ftwig.symfony.com\u002Fdoc\u002F3.x\u002Ffunctions\u002Fdump.html) to output variables using the DataFormatter. The Debug extension adds a `debug()` function which passes variables to the Message Collector,\ninstead of showing it directly in the template. It dumps the arguments, or when empty; all context variables.\n\n```twig\n{{ debug() }}\n{{ debug(user, categories) }}\n```\n\nThe Stopwatch extension adds a [stopwatch tag](https:\u002F\u002Fsymfony.com\u002Fblog\u002Fnew-in-symfony-2-4-a-stopwatch-tag-for-twig) similar to the one in Symfony\u002FSilex Twigbridge.\n\n```twig\n{% stopwatch \"foo\" %}\n    …some things that gets timed\n{% endstopwatch %}\n```\n\n## Star History\n\n[![Star History Chart](https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=fruitcake\u002Flaravel-debugbar&type=Date)](https:\u002F\u002Fwww.star-history.com\u002F#fruitcake\u002Flaravel-debugbar&Date)\n","fruitcake\u002Flaravel-debugbar 是一个为 Laravel 框架集成 PHP Debug Bar 的工具。它通过 ServiceProvider 注册和附加到输出中，支持自定义配置，并提供了一系列专为 Laravel 设计的数据收集器，如查询、路由、视图等信息的展示。此外，还集成了日志、邮件等功能以及默认的 PHP 信息、消息、时间、内存和异常收集器。该插件特别适用于开发阶段对应用进行调试与性能分析，但不建议在生产环境中启用以避免潜在的安全风险及性能影响。",2,"2026-06-11 03:16:14","top_language"]