- What is webman/blade used for?
- webman/blade is a Composer package that brings Laravel's Blade templating engine to Webman applications. It compiles .blade.php files into plain PHP classes, caches them on disk, and registers an adapter into Webman's view layer so you can render Blade views with familiar syntax. It is meant for Webman or Workerman teams that want Laravel-style templates without adopting the full Laravel framework.
- How do I install webman/blade in a Webman application?
- Install it with Composer using composer require webman/blade, then add the package's view configuration for template paths and the compiled cache directory. You also need the bootstrap wiring that binds the container and filesystem used by the Blade compiler. The installation itself is small; the larger task is auditing which Laravel-dependent directives your templates use.
- Does webman/blade support Blade layouts, sections, includes, and components?
- Yes. The package supports Blade layouts, sections, includes, and components, along with familiar Laravel-style directives and automatic escaping. Because it is built on illuminate/view, the supported feature surface follows the Blade version it pulls in. Verify component and slot behavior against your installed illuminate/view version if you rely on advanced features.
- Which Laravel Blade directives work in webman/blade?
- Core Blade syntax such as loops, conditionals, includes, layouts, and escaping works through the Blade compiler. Directives that depend on Laravel's container or helpers, such as @auth, @can, @env, route(), csrf_field(), and some component resolution, may be absent or require custom wiring in a standalone Webman app. Treat a directive inventory as part of your integration audit.
- How does template caching work in webman/blade across Webman worker processes?
- Blade compiles templates into plain PHP classes and caches them on disk, so the compiled cache path must be shared and accessible to every Workerman process. In a resident worker, a missing or stale compiled file can trigger a recompile under load or throw an exception. Pre-warm the cache during deployment and treat cache invalidation as an operational concern you own.
- Is webman/blade compatible with my PHP and Webman version?
- The package tracks illuminate/view major versions, so compatibility depends on the illuminate/* constraints in its composer.json and your PHP version. It pulls in a subset of illuminate packages including view, filesystem, events, container, and support rather than the full Laravel framework. Check the declared Composer constraints before upgrading PHP, Webman, or illuminate/view, because Blade's API surface changes between major versions.
- Can I use webman/blade outside Webman or in a standalone PHP app?
- It is designed as a bridge into Webman's view layer, so Webman is the natural fit. It can be used outside Webman if you are willing to bind your own container and filesystem and register the Blade factory yourself. That path requires more integration work and a clear understanding of how compiled templates are resolved.
- Is webman/blade production ready and actively maintained?
- The repository has limited public provenance: a small star count, no listed dependents, and a single recent release, so there is little external production evidence. You should treat adoption as an early-adopter decision and ask the maintainer about release cadence and a security disclosure path. For critical systems, plan a fallback templating layer or be prepared to vendor and patch the package.
- What happens if a compiled Blade view is missing in a long-running Webman worker?
- Because workers are long-running, the package resolves compiled templates from disk rather than holding per-request template state in memory. If a compiled file is missing or stale at request time, the worker will either recompile it under load or raise an exception, depending on the code path. Deploy pre-warmed compiled views to a shared path and monitor cache state to avoid mid-request surprises.
- Is webman/blade safe for user-generated content and how do I avoid XSS?
- Blade's double-brace syntax escapes output by default, so use {{ $value }} for untrusted data. Raw output with {!! !!} bypasses escaping entirely and remains an XSS risk, and the package does not add framework-level guardrails beyond Blade itself. Audit any directive or helper that emits HTML and avoid raw output for user-controlled content.