tuupke / laravel-finalizer

1.1.0 2026-10-27 08:47 UTC

Requires

• php: ^7.4 || ^8.0
• illuminate/support: ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0

MIT

• Mart Pluijmaekers

Published on Packagist.org on 2026-10-27 08:56 UTC

README

Laravel's implementation of finalizers (through middleware) are still synchronous with the request and will therefor increase the response-time of your application. There are many use-cases - logging for instance - for which this is not desired.

Normally speaking, standard Laravel practices dictate that a job should be used in these cases. When this is overkill, this package can be used. It provides a small wrapper around PHP's register_shutdown_function, to help with these use-cases.

Installation

Installation of this packages is done through composer.

composer require "tuupke/laravel-finalizer"

Then open config/app.php and append to the providers array:

Tuupke\Finalizer\FinalizerServiceProvider::class,

and add to the aliasses array:

'Finalizer' => Tuupke\Finalizer\FinalizerFacade::class,

Usage

From somewhere within your application you can now call: Finalizer::register($closure)) with $closure some closure executing some action. Optionally, you can provide an integer as the second parameter, which will server as the priority. The lower this priority, the earlier it is executed. When 2 closures are registered with the same priority. The closure which was registered first, will be executed first.

Example

A minimalist example which stores some contents in a file is listed below. Note that this should not be used in an actual application. When logging is required, use the Log facade.

Finalizer::register(function(){
    file_put_contents('/tmp/finalizer-test', "Second String", FILE_APPEND);
}, 2);

Finalizer::register(function(){
    file_put_contents('/tmp/finalizer-test', "First String\n", FILE_APPEND);
}, 1);

After a request has been executed which contained this code-block, the contents of /tmp/finalizer-test is:

First String
Second String

Use in non-Laravel applications

Strictly speaking, this package can also be used in non-Laravel PHP applications which use composer. But it is not recommended and defeats the purpose of this package. If you want, you can still use it. A minimal example is provided below.

// include composer autoload
require 'vendor/autoload.php';
 
// import the Finalizer Class
use Tuupke\Finalizer;
 
// Create a new instance of the Finalizer. The class itself does not provide late static binding (yet).
$finalizer = new Finalizer;
 
// register some closure.
$finalizer->register(function(){
    ... <YOUR CODE GOES HERE> ...
});

Testing

The tests run entirely in Docker, so only make and docker are required. They install the package against every supported PHP/Laravel combination and run two suites:

• CLI: checks the container binding and facade, that closures run immediately on the CLI, and that the shutdown handler runs closures by priority and logs throwables.
• HTTP: starts PHP-FPM behind nginx and performs real requests. It verifies that the response is sent before the registered closures run, and that inSyncOnExit() keeps the connection open until they have finished.

make test                       # all combinations, both suites
make test PHP=8.5 LARAVEL=13    # a single combination
make test-cli                   # only the CLI suite
make test-http                  # only the HTTP suite
make clean                      # remove the .build/ working directory

The first run pulls the required Docker images and is therefore slower.