Download the PHP package initphp/events without Composer

InitPHP Events

A small, dependency-free event / hook library for PHP. Ships both a high-level dispatcher with WordPress-style do_action-like semantics (stop the chain when a listener returns false, simulate mode, debug log) and a plain low-level EventEmitter you can instantiate and pass around like any other object.

Heads-up — v2.0 fixes a long-standing priority-ordering bug. In 1.x, listeners ran in the order they were registered, not in the order their priorities asked for. v2.0 makes priority honour its name. If your 1.x code happened to register listeners in ascending priority order, the visible behaviour does not change; if it didn't, please re-read Priorities and ordering and the v2.0 changelog.

At a glance

• Events — a static facade backed by a lazily-built singleton. Convenient for application-wide hooks where threading a dispatcher through every layer is overkill.
• Event — the high-level dispatcher itself. Adds priority-ordered dispatch with a "return false stops the chain" contract, plus optional simulate and debug modes. Use this directly when you want a dispatcher you own.
• EventEmitter — the low-level primitive. Plain on / once / emit / removeListener. No simulate, no debug, no short-circuit. Use this when you need a dispatcher with the smallest possible surface — or when you are migrating from the deprecated initphp/event-emitter package (the legacy \InitPHP\EventEmitter\* class names still work via a BC alias).

Everything is in a single PSR-4 namespace (InitPHP\Events\) and has zero runtime dependencies.

Requirements

Installation

If you are coming from initphp/event-emitter, replace your dependency — initphp/events declares a Composer replace for it and ships a class alias so the old fully-qualified names still resolve. See Migration for details.

Quick start

Output:

The listener registered with priority 99 runs before the one with priority 100 — lower numeric value means runs first. The three named constants Events::PRIORITY_HIGH (10), Events::PRIORITY_NORMAL (100), and Events::PRIORITY_LOW (200) exist for readability.

Passing arguments to listeners

Stopping the chain

A listener that returns boolean false halts the chain — subsequent listeners are not invoked and trigger() itself returns false. This is the same convention as WordPress's apply_filters short-circuit:

Working with Event directly

If you prefer a dispatcher you instantiate and pass around (easier to test, easier to scope, no global state), use Event:

Event and Events expose the same surface — Events::on(...) simply forwards to a shared Event instance.

Working with the low-level EventEmitter

For libraries that want the smallest possible surface, the underlying emitter is also public:

Differences from Event:

• emit() returns void (no short-circuit on false).
• Listener arguments come in as a single array, not as varargs.
• No simulate or debug mode.
• No singleton.

EventEmitter is what Event is built on. The same instance is reachable via $dispatcher->getEmitter() if you ever need both high-level dispatch and low-level emit on the same listener registry.

Priorities and ordering

Rules:

1. Lower numeric priority runs first. The names are about importance (high-priority work runs early); the numbers are about position.
2. Within the same priority, listeners run in registration order (FIFO).
3. Priority is global per-event — once-listeners and regular listeners are merged into a single priority-sorted queue when an event fires.
4. Event names are matched case-insensitively: on('User.Created') and emit('user.created') see the same listener.

See docs/04-priorities-and-ordering.md for the full ordering contract, including how once() interacts with the priority queue.

One-shot listeners, removal, and cleanup

The once() contract is honoured even when the chain is stopped by a false return — a one-shot listener that runs (or that would have run, but for a short-circuit earlier in the queue) is dropped after the trigger completes. See docs/05-once-and-removal.md.

Simulate mode and debug log

Event (and therefore Events) carry two opt-in instrumentation modes:

See docs/06-debug-and-simulate.md.

Public API

Full signatures and exception behaviour: docs/09-api-reference.md.

Migrating from initphp/event-emitter

The standalone initphp/event-emitter package has been merged into this one and is now deprecated. If your code currently uses \InitPHP\EventEmitter\EventEmitter, no source changes are required — this package ships a backwards-compatibility alias:

Composer will not install both packages side-by-side because initphp/events:^2.0 declares a replace for initphp/event-emitter.

When you next touch the code, prefer the new canonical namespace:

The alias is intended as a transition aid and may be removed in a future major release. One important behaviour change that comes with v2.0: in 1.x, EventEmitter::emit() had a bug where the entire listeners array was passed to call_user_func_array instead of each individual listener, so emitted events silently fired no listeners at all. That is fixed in 2.0 — if you had quietly broken emit() calls in 1.x, they will now actually run their listeners.

See docs/07-migration-from-event-emitter.md for the full migration checklist.

Documentation

The full guide lives under docs/:

1. Getting started
2. The Events facade
3. Using EventEmitter directly
4. Priorities and ordering
5. Once-listeners, removal, and cleanup
6. Debug and simulate modes
7. Migrating from initphp/event-emitter
8. Recipes (plugin systems, request lifecycle, WordPress-style hooks)
9. API reference

Development

CI runs the test suite across PHP 7.3 – 8.4 and also lints the source on PHP 5.6 / 7.0 / 7.1 / 7.2 so the php >= 5.6 library contract stays honest.

Contributing & Security

• Contributing guidelines
• Code of Conduct
• Security policy

Credits

• Muhammet ŞAFAK

License

Released under the MIT License.