- What is pxlrbt/php-scoper-prefix-remover used for?
- It removes PHP-Scoper prefixes from prefixed class names and namespace strings so you can inspect or debug scoped code. It is useful after running php-scoper when you need unprefixed references back in generated artifacts, logs, or traces. It is a build-pipeline utility, not a general Laravel runtime package.
- How do I install pxlrbt/php-scoper-prefix-remover?
- Install it with Composer, typically under require-dev because it belongs in build and debugging workflows. Pin an exact version because the package has no recent release and compatibility is unproven. Check the PHP constraint in its composer.json and confirm it runs on your CI image before relying on it.
- Does pxlrbt/php-scoper-prefix-remover work with Laravel?
- Not in any meaningful framework sense; it has no Laravel service provider or runtime integration described. In a conventional Laravel application that resolves dependencies through Composer, PHP-Scoper never runs and this package has no role. It may fit a white-label Laravel package distribution that is scoped to avoid class collisions in a host application.
- Is pxlrbt/php-scoper-prefix-remover GPL licensed?
- The evaluation identifies it as GPL-3.0, which is strong copyleft. Build-time-only use that never enters the shipped artifact limits exposure to tooling, but a runtime exception handler or Monolog processor in distributed output raises serious copyleft concerns. Have legal clear the actual consumption model before adoption.
- Does pxlrbt/php-scoper-prefix-remover ship a runtime component?
- The critical question is whether it is only a build-time post-processing shim or also ships runtime code into the scoped artifact. The provided context does not establish a runtime surface, so verify before assuming. That single answer determines whether GPL-3.0 propagates to your distributed work.
- Which PHP-Scoper versions does pxlrbt/php-scoper-prefix-remover support?
- Compatibility is unproven; the package has had no release since 2021-11-30 and no public validation against current PHP 8.x or PHP-Scoper versions. Prefix removal also couples to PHP-Scoper configuration and output conventions, which are not a stable public contract. Test against your exact PHP-Scoper version and configured prefix literal in CI.
- Can I configure custom prefixes, and does it read my scoper.inc.php?
- The context does not confirm configurable prefix-removal logic or whether the package reads your existing scoper.inc.php. If it requires duplicate configuration, that configuration can drift from your actual PHP-Scoper setup. Confirm support for custom prefixes, allow or deny lists, regex, and nested arrays before depending on it.
- How should I test pxlrbt/php-scoper-prefix-remover before using it?
- Treat it as a pipeline stage: add it under require-dev with an exact version pin, invoke it immediately after the php-scoper step, and diff the produced artifact against a stored baseline. Assert that intended prefixes are removed and that legitimate non-prefixed class names remain intact. Because prefix removal is literal string manipulation, include tests for your exact prefix literal and PHP version.
- Is pxlrbt/php-scoper-prefix-remover maintained?
- It has a single maintainer, roughly 10 stars, zero dependents, and no release since November 2021. That signals abandonment risk, and adoption could make you the de facto maintainer. Budget for vendoring or reimplementing the small prefix-removal logic as the likely landing zone.
- What are alternatives to pxlrbt/php-scoper-prefix-remover?
- The provided context does not name a maintained alternative. Because the package is small, a fork or a local build-step implementation may be the practical fallback, especially given GPL-3.0 concerns. Validate any alternative against your PHP-Scoper version and a stored artifact baseline.