Php Debugger to run in terminal to debug your code easily.

Overview

Build Status Code Climate HitCount Coverage GitHub license GitHub tag Packagist

logo

What is Dephpugger?

Dephpugger (read depugger) is an open source lib to make a debug in php direct in terminal, without necessary configure an IDE. The dephpugger run in Php Built in Server using another command. You can use for:

Web applications

Lumen in example

dephpugger web Image 1.0 - Screenrecord for debug web

Cli Scripts

dephpugger Image 1.1 - Screenrecord for debug cli scripts

Another example

dephpugger

Install

To install you must run this code (using the composer).

$ composer require tacnoman/dephpugger

Install globally

In Linux or Mac Os X

Run this command:

$ composer global require tacnoman/dephpugger

And add in your ~/.bash_profile.

export PATH=$PATH:$HOME/.config/composer/vendor/bin

Now, run source ~/.bash_profile and you can run the commands using only $ dephpugger.

In Windows

Sorry for this :/ I don't have Windos SO to run the Dephpugger, but I'm waiting your Pull Request to solve this ;D

But you can use Docker

Using phar file

$ wget https://raw.githubusercontent.com/tacnoman/dephpugger/master/dephpugger.phar -O dephpugger
$ chmod +x ./dephpugger
$ mv ./dephpugger /usr/local/bin/dephpugger

Or installing via curl

$ curl https://raw.githubusercontent.com/tacnoman/dephpugger/master/installer.sh | bash

Install XDebug

To install XDebug in Linux you must run:

$ sudo apt-get install php-7.2-cli php-dev php-pear
$ sudo pecl install xdebug

Find the last line, similar to: You should add "zend_extension=/usr/lib/php/20170718/xdebug.so" to php.ini and copy to your php.ini file. To get the php.ini file, you can run:

$ php --info | grep php.ini

Configuration File (php.ini) Path => /etc/php/7.2/cli
Loaded Configuration File => /etc/php/7.2/cli/php.ini

Copy the zend_extension=/usr/lib/php/20170718/xdebug.so to last line in /etc/php/7.2/cli/php.ini.

Docker

$ docker run --rm -p 8888:8888 tacnoman/dephpugger:latest server

Dependencies

  • PHP 7.0 or more (not tested in older versions)
  • Xdebug activate
  • A Plugin for your browser (If you want to debug a web application)

Plugins for

You can run this commands to check your dependencies:

$ vendor/bin/dephpugger requirements
$ vendor/bin/dephpugger info # To get all values setted in xDebug

# Or in global

$ dephpugger requirements
$ dephpugger info

Usage

To usage you must (after installation) run two binaries in vendor/bin folder.

$ php vendor/bin/dephpugger debugger # Debugger waiting debug
$ php vendor/bin/dephpugger server   # Server running in port 8888

# Or in global

$ dephpugger debugger
$ dephpugger server

You must run in two different tabs (in next version you'll can run in an uniq tab). After run theese commands, you need to put the follow line in your code:

<?php
# ...
xdebug_break(); # This code is a breakpoint like ipdb in Python and Byebug in Ruby
# ....

Now, you can open in your browser the page (localhost:8888/[yourPage.php]). When you request this page your terminal will start in breakpoint (like the image 1.0).

To debugger a php script, you could run:

$ php vendor/bin/dephpugger cli myJob.php

# Or in global

$ dephpugger cli myJob.php

Comands after run

When you stop in a breakpoint you can make theese commands:

Command Alias Explanation
next n To run a step over in code
step s To run a step into in code
set <cmd>:<value> Change verboseMode or lineOffset in runtime
continue c To continue script until found another breakpoint or finish the code
list l Show next lines in script
list-previous lp Show previous lines in script
help h Show help instructions
$variable Get a value from a variable
$variable = 33 Set a variable
my_function() Call a function
dbgp(<command>) To run a command in dbgp
quit q Exit the debugger

Configuration (is simple)

The Dephpugger project has default options like a port, host, socket port, etc. You can change this values adding a file .dephpugger.yml in root directory project. You can create in your .dephpugger.yml file the configurations. Like this:

--- 
debugger: 
  host: mysocket.dev # default: 0.0.0.0
  port: 9002 # default: 9005
  lineOffset: 10 # default: 6
  verboseMode: false # default: false
  historyFile: ~/.dephpugger_history # default: .dephpugger_history
server:
  host: myproject.dev # default: 0.0.0.0
  port: 8080 # default: 8888
  path: ./public/ # default: null
  file: index.php # default: null

Theese values will replace the default configuration.

Full documentation

To see the full documentation click here.

How to use with phpunit, behat, codeception and others

The documentation to use, click here.

Run tests

$ composer test
$ composer lint

Bugs?

Send me an email or open an issue:

Renato Cassino - Tacnoman - <[email protected]>

See our changelog

Articles and Videos

  1. How debug Drupal applications using Dephpugger
  2. Dephpugger in Sinapore event
  3. How debug applications with Dephpugger
  4. Debugging with Dephpugger
Comments
  • Cant run requirements

    Cant run requirements

    Hi I need some help here. I run dephpugger requirements and this is what i get

    Fatal error: Uncaught Error: Class 'Dephpug\Console\CliCommand' not found in /root/.composer/vendor/tacnoman/dephpugger/src/Dephpug/Dephpugger.php:28
    Stack trace:
    #0 /root/.composer/vendor/tacnoman/dephpugger/bin/dephpugger(48): Dephpug\Dephpugger->run()
    #1 {main}
      thrown in /root/.composer/vendor/tacnoman/dephpugger/src/Dephpug/Dephpugger.php on line 28
    The command '/bin/sh -c dephpugger requirements' returned a non-zero code: 255
    

    any idea what is wrong?

    opened by mosesliao 5
  • Step up/down stack with u / d

    Step up/down stack with u / d

    I use pdbpp for python, and one of the most amazing features it has is the ability to use u and d keys to traverse the calls (I'm assuming this is stack walking, but may be wrong).

    I don't expect this will get done, but I think it'd be a nice feature so maybe someone will see this and pick it up?

    opened by Lewiscowles1986 4
  • Which version of Laravel/Lumen is supported?

    Which version of Laravel/Lumen is supported?

    Currently, having composer dependency issues when adding dephpugger to a new install of Laravel 5.7.13

    Problem 1 - Conclusion: don't install tacnoman/dephpugger 1.2.2 - Conclusion: don't install tacnoman/dephpugger 1.2.1 - Conclusion: remove symfony/console v4.1.7 - Installation request for tacnoman/dephpugger ^1.2 -> satisfiable by tacnoman/dephpugger[1.2.0, 1.2.1, 1.2.2]. - Conclusion: don't install symfony/console v4.1.7 - tacnoman/dephpugger 1.2.0 requires symfony/console ^3.2 -> satisfiable by symfony/console[3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v3.2.0, v3.2.0-BETA1, v3. 2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-B ETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.17, v3.3.18, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v3.4.1, v3.4.10, v3.4.11, v3.4.12, v3.4.13, v3.4. 14, v3.4.15, v3.4.16, v3.4.17, v3.4.18, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].

    Thanks

    opened by jonwhittlestone 3
  • Add plugins in composer autoload file list

    Add plugins in composer autoload file list

    What this PR do?

    Force to declare plugin classes adding source files into file list of autoload section in composer.json.

    What this PR solve?

    The plugins are loaded dynamically using get_declared_class function. The problem is that these class will never be until be used.

    This commit just add this files in composer autoload files to be declared when autoload.php be included.

    This problem was referenced in #20

    opened by ricardotulio 3
  • Call to undefined function Dephpug\Dbgp\socket_create()

    Call to undefined function Dephpug\Dbgp\socket_create()

    I get a Fatal error when executing dephpugger. call vendor/bin/dephpugger.bat server works, but call vendor/bin/dephpugger.bat debugger throws an error:

    Server - Version: v1.1.1
    PHP Fatal error:  Uncaught Error: Call to undefined function Dephpug\Dbgp\socket_create() in C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\src\Dephpug\Dbgp\Server.php:33
    Stack trace:
    #0 C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\src\Dephpug\Dbgp\Client.php(43): Dephpug\Dbgp\Server->startClient('localhost', 9005)
    #1 C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\src\Dephpug\Core.php(35): Dephpug\Dbgp\Client->startClient('localhost', 9005)
    #2 C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\console\DebuggerCommand.php(32): Dephpug\Core->run()
    #3 C:\xampp\htdocs\myProject\vendor\symfony\console\Command\Command.php(264): Dephpug\Console\DebuggerCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
    #4 C:\xampp\htdocs\myProject\vendor\symfony\console\Application.php(888): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
    #5 in C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\src\Dephpug\Dbgp\Server.php on line 33
    
    Fatal error: Uncaught Error: Call to undefined function Dephpug\Dbgp\socket_create() in C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\src\Dephpug\Dbgp\Server.php on line 33
    
    Error: Call to undefined function Dephpug\Dbgp\socket_create() in C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\src\Dephpug\Dbgp\Server.php on line 33
    
    Call Stack:
        0.4045     359904   1. {main}() C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\bin\dephpugger:0
        0.4718    2021656   2. Symfony\Component\Console\Application->run() C:\xampp\htdocs\myProject\vendor\tacnoman\dephpugger\bin\dephpugger:89
    
    opened by TekkCraft 3
  • composer fails

    composer fails

    composer require tacnoman/dephpugger Using version ^1.5 for tacnoman/dephpugger Root package 'tacnoman/dephpugger' cannot require itself in its composer.json

    Mac OSX 10.14, PHP 7.1.3

    opened by bretweinraub 2
  • how to run PHP scripts with command-line arguments

    how to run PHP scripts with command-line arguments

    I'm trying to debug the command-line program invocation

    $ /usr/share/arcanist/scripts/arcanist.php --trace install-certificate --conduit-uri=https://phabricator.kde.org/api/conduit.ping
    

    I can't see how to provide command line arguments to the PHP script I supply to the dephpugger cli command. I've checked dephpugger help cli usage help and your online docs.

    Update: it seems putting the PHP script and its command-line arguments in quotes as a single argument works. Please mention this to https://dephpugger.com/docs/usage/commands_to_run and add to the usage for dephpugger cli --help a line like

    Arguments: file The php script file or 'file arg1 arg2 ...' The php script file and its command-line arguments in quotes.

    opened by skierpage 2
  • Failed building a docker

    Failed building a docker

    Hi, I have this following Dockerfile that I create to make a dephpugger docker image. But it keeps failing

    Step 15/15 : RUN dephpugger requirements
     ---> Running in 68057bd46031
    
    Warning: require(vendor/autoload.php): failed to open stream: No such file or directory in /root/.composer/vendor/tacnoman/dephpugger/bin/dephpugger on line 27
    
    Call Stack:
        0.0002     350912   1. {main}() /root/.composer/vendor/tacnoman/dephpugger/bin/dephpugger:0
    
    
    Fatal error: require(): Failed opening required 'vendor/autoload.php' (include_path='.:/usr/local/lib/php') in /root/.composer/vendor/tacnoman/dephpugger/bin/dephpugger on line 27
    
    Call Stack:
        0.0002     350912   1. {main}() /root/.composer/vendor/tacnoman/dephpugger/bin/dephpugger:0
    
    The command '/bin/sh -c dephpugger requirements' returned a non-zero code: 255
    

    what could be the problem?

    opened by mosesliao 2
  • Fatal error: Uncaught Error: Call to undefined function socket_create()

    Fatal error: Uncaught Error: Call to undefined function socket_create()

    Context

    Problem when try to run $ dephpugger debug command.

    Expected behavior

    Just work as needed.

    Current behavior

    When I tried to run $ dephpugger debug, I receive the following message:

    Fatal error: Uncaught Error: Call to undefined function Dephpug\Dbgp\socket_create()
    

    It ocurr because socket_create inst imported in Dephpug/Dbgp/Server.php.

    opened by ricardotulio 2
  • Plugins not being loaded

    Plugins not being loaded

    The dephpugger debug does not work due some problem with autoload.

    I observed that get_declared_classes function at line https://github.com/tacnoman/dephpugger/blob/master/src/Dephpug/PluginReflection.php#L38 don't retrieve classes defined on src/Dephpug/Command and src/Dephpug/Parser directory.

    Seems some problem with autoload.

    I make all working with the follow change at bin/dephpugger:

    $command_dir = __DIR__ .
        DIRECTORY_SEPARATOR . '..' .
        DIRECTORY_SEPARATOR . 'src' .
        DIRECTORY_SEPARATOR . 'Dephpug' .
        DIRECTORY_SEPARATOR . 'Command';
    
    $command_files = glob($command_dir . DIRECTORY_SEPARATOR . '' . '*.php');
    
    foreach ($command_files as $filename) {
        require_once $filename;
    }
    
    $parser_msgs_dir = __DIR__ .
        DIRECTORY_SEPARATOR . '..' .
        DIRECTORY_SEPARATOR . 'src' .
        DIRECTORY_SEPARATOR . 'Dephpug' .
        DIRECTORY_SEPARATOR . 'Parser';
    
    $parser_msgs_files = glob($parser_msgs_dir . DIRECTORY_SEPARATOR . '' . '*.php');
    
    foreach ($parser_msgs_files as $filename) {
        require_once $filename;
    }
    

    Given that I'm not a PHP expert, maybe a better solution exists.

    opened by marciol 2
  • Fix binary to be used on development enviroment

    Fix binary to be used on development enviroment

    What this PR do?

    Basically, this PR remove responsibility of check and include files from bin/dephpugger file. Its done adding avoid directories to composer.json and separate some functions to its specific files. Also change way that autoload.php file is added.

    What this PR solve?

    Fix #16.

    Sorry for my english, if something is not so clearly, I'm open to discuss.

    opened by ricardotulio 2
  • Support for XDebug 3

    Support for XDebug 3

    With latest version of XDebug you'll find some properties have been updated/renamed.

    This has meant (until there is a newer version of dephpugger that supports XDebug 3) I had to manually update vendor/tacnoman/dephpugger/src/Dephpug/Console/CliCommand.php with the renamed fields (see https://xdebug.org/docs/errors#CFG-C-CHANGED and the linked upgrade guide for details).

    The summary of those changes being:

    • -dxdebug.remote_enable=1 -> -dxdebug.mode=debug
    • -dxdebug.remote_mode=req -> -dxdebug.start_with_request=trigger
    • -dxdebug.remote_port -> -dxdebug.client_port
    • -dxdebug.remote_host -> -dxdebug.client_host
    - $command = "{$configVar} {$phpPath} -dxdebug.remote_enable=1 -dxdebug.remote_mode=req -dxdebug.remote_port={$debuggerPort} -dxdebug.remote_host=127.0.0.1 {$phpFile}";
    + $command = "{$configVar} {$phpPath} -dxdebug.mode=debug -dxdebug.start_with_request=trigger -dxdebug.client_port={$debuggerPort} -dxdebug.client_host=127.0.0.1 {$phpFile}";
    
    opened by Integralist 1
  • dephpugger requirements => Uncaught Error: Call to undefined function Dephpug\Console\concerns\xdebug_is_enabled() in /home/hal/.config/composer/vendor/tacnoman/dephpugger/src/Dephpug/Console/concerns/PhpInfo.php:66

    dephpugger requirements => Uncaught Error: Call to undefined function Dephpug\Console\concerns\xdebug_is_enabled() in /home/hal/.config/composer/vendor/tacnoman/dephpugger/src/Dephpug/Console/concerns/PhpInfo.php:66

    The full output is: ✔️ Your PHP version is 7.0 or more ✔️ XDebug is installed. ✔️ Sockets extension is installed. PHP Fatal error: Uncaught Error: Call to undefined function Dephpug\Console\concerns\xdebug_is_enabled() in /home/hal/.config/composer/vendor/tacnoman/dephpugger/src/Dephpug/Console/concerns/PhpInfo.php:66 Stack trace: #0 /home/hal/.config/composer/vendor/tacnoman/dephpugger/src/Dephpug/Console/RequirementsCommand.php(36): Dephpug\Console\concerns\PhpInfo->xdebugIsActive() #1 /home/hal/.config/composer/vendor/symfony/console/Command/Command.php(255): Dephpug\Console\RequirementsCommand->execute() #2 /home/hal/.config/composer/vendor/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run() #3 /home/hal/.config/composer/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand() #4 /home/hal/.config/composer/vendor/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun() #5 /home/hal/.config/composer/vendor/tacnoman/dephpugger/src/Dephpug/Dephpugger.php(33): Symfony\Component\Console\Application->run() #6 /home/hal/.config/composer in /home/hal/.config/composer/vendor/tacnoman/dephpugger/src/Dephpug/Console/concerns/PhpInfo.php on line 66

    This is on ubuntu v20.10 with newly installed apache2, php 7.4.9, and /etc/php/7.4/mods-available/xdebug.ini: zend_extension=/usr/lib/php/20190902/xdebug.so xdebug.log="/opt/lampp/xdb-logs/xdebug.log" xdebug.log_level=7 xdebug.client_host=127.0.0.1 xdebug.client_port=9005 xdebug.debug_mode=develop,debug,trace xdebug.start_with_request=trigger xdebug.collect_params=3

    and /etc/php/7.4/apache2/conf.d/20-xdebug.ini -> /etc/php/7.4/mods-available/xdebug.ini /etc/php/7.4/cli/conf.d/20-xdebug.ini -> /etc/php/7.4/mods-available/xdebug.ini

    Thanks in advance for your help.

    opened by HalMorris 1
  • Getting Dephpugger to work with PHPunit from the command line

    Getting Dephpugger to work with PHPunit from the command line

    Hi, I can't seem to get xdebug_break() to start from the command line. I have reviewed the following documentation https://dephpugger.com/docs/usage/running_with_phpunit, and it states to add thexdebug_break(); in the code where you want to start troubleshooting. After adding the function to the PHPUnit test and running the command, it won't work. Can you see from the information below why it won't break?

    When I have added the function https://github.com/purencool/search/blob/master/tests/SSearchGetSearchResultsTest.php.

      public function testAPartialStringRequest()
      {
        xdebug_break(); # <-- Add this line
        $testObj = new Purencool\TestData\TestData();
        $obj = new Purencool\Search\Search($testObj::defaultArray());
    

    To run the tests from the command line I run the following,

    ./vendor/bin/dephpugger cli  ./vendor/bin/phpunit
    
    

    The tests run, but dephpugger never breaks.

    Time: 72 ms, Memory: 6.00 MB
    
    There was 1 failure:
    
    1) SSearchGetSearchResultsTest::testAPartialStringRequest
    Failed asserting that false is true.
    
    /somepath/search/tests/SSearchGetSearchResultsTest.php:46
    
    FAILURES!
    Tests: 28, Assertions: 42, Failures: 1.
    
    
    

    This is my version of php and xdebug

    $ php -v
    PHP 7.3.20 (cli) (built: Jul  9 2020 23:55:30) ( NTS )
    Copyright (c) 1997-2018 The PHP Group
    Zend Engine v3.3.20, Copyright (c) 1998-2018 Zend Technologies
        with Zend OPcache v7.3.20, Copyright (c) 1999-2018, by Zend Technologies
        with Xdebug v2.9.6, Copyright (c) 2002-2020, by Derick Rethans
    
    
    $ ./vendor/bin/dephpugger cli -vvv  ./vendor/bin/phpunit
    Running file script: ./vendor/bin/phpunit
    Command: XDEBUG_CONFIG="idekey=PHPSTORM" /usr/local/Cellar/[email protected]/7.3.20/bin/php -dxdebug.remote_enable=1 -dxdebug.remote_mode=req -dxdebug.remote_port=9005 -dxdebug.remote_host=127.0.0.1 ./vendor/bin/phpunit
    PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
    
    
    
    opened by purencool 3
  • This problem in Windows 10 with laragon

    This problem in Windows 10 with laragon

    imagen Warning: array_replace_recursive(): Expected parameter 2 to be an array, string given in C:\Users\Asus\AppData\Roaming\Composer\vendor\tacnoman\dephpugger\src\Dephpug\Config.php on line 53

    Call Stack: 0.4055 409032 1. {main}() C:\Users\Asus\AppData\Roaming\Composer\vendor\tacnoman\dephpugger\bin\dephpugger:0 0.4198 1121072 2. Dephpug\Dephpugger->run() C:\Users\Asus\AppData\Roaming\Composer\vendor\tacnoman\dephpugger\bin\dephpugger:27 0.4299 1927784 3. Symfony\Component\Console\Application->run() C:\Users\Asus\AppData\Roaming\Composer\vendor\tacnoman\dephpugger\src\Dephpug\Dephpugger.php:33 0.4365 2264968 4. Symfony\Component\Console\Application->doRun() C:\Users\Asus\AppData\Roaming\Composer\vendor\symfony\console\Application.php:147 0.4375 2268344 5. Symfony\Component\Console\Application->doRunCommand() C:\Users\Asus\AppData\Roaming\Composer\vendor\symfony\console\Application.php:271 0.4375 2268344 6. Dephpug\Console\ServerCommand->run() C:\Users\Asus\AppData\Roaming\Composer\vendor\symfony\console\Application.php:1001 0.4379 2269976 7. Dephpug\Console\ServerCommand->execute() C:\Users\Asus\AppData\Roaming\Composer\vendor\symfony\console\Command\Command.php:255 0.4384 2279888 8. Dephpug\Config->configure() C:\Users\Asus\AppData\Roaming\Composer\vendor\tacnoman\dephpugger\src\Dephpug\Console\ServerCommand.php:30 0.4472 2626520 9. array_replace_recursive() C:\Users\Asus\AppData\Roaming\Composer\vendor\tacnoman\dephpugger\src\Dephpug\Config.php:53

    Variables in local scope (#8): $config = 'server: omnio.back.test path: ./public/ port: 80 file: index.php'


    | __ \ | | | | | | ___ _ __ | |__ _ __ _ _ __ _ __ _ ___ _ __ | | | |/ _ \ '_ | '_ | '_ | | | |/ |/ _ |/ _ \ '| | || | __/ |) | | | | |) | || | (| | (| | / | |/ _| .__/|| || .__/ _,|_, |_, |___|| | | | | / | / | || || |/ |/

                                   Server - Version: v1.5.2
    

    Running command: D:\laragon\bin\php\php-7.3.12-nts-Win32-VC15-x64\php.exe -S : -t d:\laragon\www\omnio.back -dxdebug.remote_enable=1 -dxdebug.remote_mode=req -dxdebug.remote_port= -dxdebug.remote_host= -dxdebug.remote_connect_back=0

    Access in :

    Invalid address: :

    opened by jlhumerez 2
Owner
Renato Cassino
Software engineer at olx.com.br
Renato Cassino
Xdebug — Step Debugger and Debugging Aid for PHP

Xdebug Xdebug is a debugging tool for PHP. It provides step-debugging and a whole range of development aids, such as stack traces, a code profiler, fe

Xdebug 2.8k Jan 3, 2023
The Interactive PHP Debugger

The interactive PHP debugger Implemented as a SAPI module, phpdbg can exert complete control over the environment without impacting the functionality

Joe Watkins 841 Oct 9, 2022
Dontbug is a reverse debugger for PHP

Dontbug Debugger Dontbug is a reverse debugger (aka time travel debugger) for PHP. It allows you to record the execution of PHP scripts (in command li

Sidharth Kshatriya 709 Dec 30, 2022
Simple php debugger

Debugger Description Simple debugger for php Requirements PHP 5.5+ to 8.0 Usage new \Debugger\Debugger( true, // work mode [false - disable, 'FILE' -

null 0 Aug 10, 2022
A Laravel Package to integrate Nette Tracy Debugger

Nette Tracy for Laravel 5 Better Laravel Exception Handler Features Visualization of errors and exceptions Debugger Bar (ajax support @v1.5.6) Excepti

Recca Tsai 383 Dec 6, 2022
Yet Another Swoole Debugger

English | 中文 yasd Yet Another Swoole Debugger. document How to use it build You'll need to install the Boost library first. macOS: brew install boost

Swoole Project 319 Dec 25, 2022
Slim Framework Tracy Debugger Bar

Slim Framework Tracy Debugger Bar configure it by mouse now in package: Panel Description Slim Framework - Slim Environment RAW data Slim Container RA

null 72 Aug 29, 2022
Ray server is a beautiful, lightweight php app build on Laravel that helps you debug your app. It runs without installation on multiple platforms.

RayServer is a beautiful, lightweight web server built on Laravel and VueJs that helps debugging your app. It runs without installation on multiple platforms.

Pavel Buchnev 310 Jan 2, 2023
A simple Craft module, inspired by Mildly Geeky's "Kint", to debug Twig within your browser

A simple Craft module, inspired by Mildly Geeky's "Kint", to debug Twig within your browser

TrendyMinds 4 Feb 2, 2022
Debug bar for PHP

PHP Debug Bar Displays a debug bar in the browser with information from php. No more var_dump() in your code! Features: Generic debug bar Easy to inte

Maxime Bouroumeau-Fuseau 4k Jan 8, 2023
PHP Debug Console

PHP Console A web console to try your PHP code into Creating a test file or using php's interactive mode can be a bit cumbersome to try random php sni

Jordi Boggiano 523 Nov 7, 2022
Laravel Debugbar (Integrates PHP Debug Bar)

Laravel Debugbar This is a package to integrate PHP Debug Bar with Laravel. It includes a ServiceProvider to register the debugbar and attach it to th

Barry vd. Heuvel 14.8k Jan 9, 2023
An elegant debug assistant for the Laravel framework.

Introduction Laravel Telescope is an elegant debug assistant for the Laravel framework. Telescope provides insight into the requests coming into your

The Laravel Framework 4.4k Dec 27, 2022
Extends the Debug Bar plugin for the Sophi.io service

Debug Bar for Sophi.io Extends the Debug Bar plugin for the Sophi.io service Requirements PHP 7.4+ WordPress 5.6+ Sophi.io 1.1.0+ Debug Bar 1.0+ Insta

10up 2 Jun 22, 2022
Handle PHP errors, dump variables, execute PHP code remotely in Google Chrome

PHP Console server library PHP Console allows you to handle PHP errors & exceptions, dump variables, execute PHP code remotely and many other things u

Sergey 1.4k Dec 25, 2022
😎 Tracy: the addictive tool to ease debugging PHP code for cool developers. Friendly design, logging, profiler, advanced features like debugging AJAX calls or CLI support. You will love it.

Tracy - PHP debugger Introduction Tracy library is a useful helper for everyday PHP programmers. It helps you to: quickly detect and correct errors lo

Nette Foundation 1.6k Dec 23, 2022
Clockwork - php dev tools in your browser - server-side component

Clockwork is a development tool for PHP available right in your browser. Clockwork gives you an insight into your application runtime - including requ

its 4.8k Dec 29, 2022
Generate Laravel test factories from your existing models

Laravel Test Factory Generator php artisan generate:model-factory This package will generate factories from your existing models so you can get starte

Marcel Pociot 923 Dec 16, 2022
Test your routes without hassle

Laravel Api Tester Live demo Try it out: laravel-api-tester.asva.by Docs Those are short and easy to read. Take a look. Interface FAQ Installation Req

Yauheni Prakopchyk 343 Nov 6, 2022