bear/package

BEAR.Sunday application framework package

1.20.1 2026-01-24 20:35 UTC

Requires

• php: ^8.2
• ext-hash: *
• aura/cli: ^2.2
• bear/app-meta: ^1.9
• bear/query-repository: ^1.13
• bear/resource: ^1.27
• bear/streamer: ^1.4
• bear/sunday: ^1.8
• koriym/http-constants: ^1.2
• koriym/psr4list: ^1.3
• monolog/monolog: ^1.25 || ^2.0 || ^3.0
• psr/cache: ^1.0 || ^2.0 || ^3.0
• psr/log: ^1.1 || ^2.0 || ^3.0
• ray/aop: ^2.19
• ray/compiler: ^1.13
• ray/di: ^2.19.3
• ray/object-visual-grapher: ^1.0
• ray/psr-cache-module: ^1.5.1
• symfony/cache: ^v6.4 || ^v7.2

Requires (Dev)

• bamarni/composer-bin-plugin: ^1.8
• phpunit/phpunit: ^11.0

MIT

• BEAR.Package Contributors

• framework
• aop
• rest
• di

README

Overview

BEAR.Sunday is a resource-oriented framework that defines the interfaces and abstractions for the application lifecycle — resource handling, dependency injection, and AOP interception. It does not include concrete implementations for routing, caching, error handling, or compilation.

BEAR.Package is the implementation package for BEAR.Sunday. It provides the production-ready bindings that turn those interfaces into a working application: HTTP routing, DI container compilation, query repository caching, application/vnd.error+json error pages, PSR-3 logging, and context-based module loading.

What This Package Provides

Concern	Implementation
Routing	WebRouter (HTTP), CliRouter (CLI)
Error Handling	DevVndErrorPage / ProdVndErrorPage (application/vnd.error+json)
Caching	QueryRepository integration, PSR-6 cache
Compilation	DI container compiled to PHP scripts, preload file, autoload optimization
Logging	PsrLoggerModule (Monolog, PSR-3)
Context Modules	ProdModule, ApiModule, CliModule, HalModule

Architecture

Context-Based DI Binding Override

Instead of switching behavior with a global MODE constant and conditionals, BEAR.Package uses a multi-dimensional context string to compose DI modules. Each segment of the context corresponds to a module, and later modules override the bindings of earlier ones.

For example, the context "prod-api-app" is split by -, reversed, and each segment resolves to a Module class:

1. app — AppModule (loaded first; base bindings + PackageModule)
2. api — ApiModule (overrides default scheme binding to app://self)
3. prod — ProdModule (overrides cache, error handler, and compilation bindings)

The framework's behavior changes entirely through binding overrides — no if branches on environment values. Each segment is resolved in order:

1. App namespace first: {AppName}\Module\{Context}Module
2. Framework fallback: BEAR\Package\Context\{Context}Module

This allows applications to override any context module while falling back to the framework defaults.

Documentation

Documentation is available at https://bearsunday.github.io/.