NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #4874 most downloaded on Packagist
Resource Watcher - Lightweight edition of henrikbjorn/lurker with no dependencies
Latest stable
1.3.0
Last release 6 years ago
no release in 18 months
Ships fairly regularly
a new release about every 2.4 years
Some releases are documented
notes for 1 of 4 stable releases
Nothing withdrawn
no release was ever pulled
13 years old
4 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Disable InotifyTracker due to faulty rename handling. Update tracker …
Disable InotifyTracker due to faulty rename handling. Update tracker …
totten/lurkerlite 1.3 is a fork of henrikbjorn/lurker 1.2. It primarily aims to address dependency-management
issues which have been outstanding for multiple years -- and also to merge some of the PR backlog.
This revision should be a drop-in replacement unless you customize the event-dispatcher. Compare:
ResourceWatcher creates its own internal event-dispatcher.
If you use this default, then the update should be a drop-in replacement.ResourceWatcher previously accepted an optional argument based on
\Symfony\Component\EventDispatcher\EventDispatcherInterface. This may have been useful for glueing into another
dispatcher/application. This also makes lurker a dependency-bottleneck, and it is not supported by lurkerlite.
If a system attempts to use a Symfony EventDispatcher, lurkerlite will ignore it and emit a warning
(E_USER_DEPRECATED).If you need to bridge lurker with another event system, then here is an alternative technique: subscribe to the
wildcard event (all) and then delegate to your preferred dispatcher. This technique should work equally well on
lurker or lurkerlite, and it should work with diverse event systems. Pseudocode:
$w = new \Lurker\ResourceWatcher();
$w->addListener('all', function(\Lurker\Event\FilesystemEvent $e) use ($myDispatcher) {
$myEventName = 'resource_watcher.' . $e->getTrackedResource()->getTrackingId();
$myEvent = new MyFilesystemEvent($e->getResource(), ...);
$myDispatcher->dispatch($myEventName, $myEvent);
});
More detailed list of changes:
symfony/config (https://github.com/flint/Lurker/pull/22)symfony/event-dispatcher. (This is an alternative
to https://github.com/flint/Lurker/pull/29 or https://github.com/flint/Lurker/pull/31.)RecursiveIteratorTracker as the default -- effectively disabling InotifyTracker
(unless you specifically opt into it). InotifyTrackerTest has been reporting failures (eg https://github.com/flint/Lurker/pull/24 and
https://github.com/flint/Lurker/issues/32). The reason is unclear, but it is not any kind of obvious,
bisectable cause. (Perhaps it was an upstream change in PHP, pecl/inotify, or Linux? Or perhaps it never
fully worked?) Turn it off until someone figures out how to fix it.Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.