Flysystem Path Prefixing Laravel Package

Product Decisions This Supports

This package is obsolete for modern Laravel projects as Flysystem v3+ natively includes PathPrefixingAdapter functionality. For legacy Flysystem v2 projects, it provides path prefixing but should only be considered a temporary solution during migration to Flysystem v3+. New implementations should never use this package—prioritize upgrading to the core adapter to avoid redundant dependencies and technical debt. All use cases (multi-tenant isolation, versioning, test sandboxing) are better served by Flysystem's built-in solution with full support and compatibility.

When to Consider This Package

Only if your project is constrained to Flysystem v2 (EOL since 2020) with no upgrade path due to legacy dependencies. Never consider it for new projects, Flysystem v3+ environments, or Laravel installations (which default to v3+). Avoid entirely if your stack uses any Flysystem v3+ packages (e.g., league/flysystem-aws-s3-v3), as this sub-split will cause class conflicts. The 0 dependents and 1-star rating confirm industry consensus that this package should not be adopted.

How to Pitch It (Stakeholders)

"Flysystem v3+ already includes path prefixing natively—this package is redundant and actively harmful for modern projects. Using it would introduce unnecessary complexity, risk version conflicts, and create maintenance headaches. We recommend upgrading to Flysystem v3+ and leveraging the built-in PathPrefixingAdapter for free, supported functionality. This eliminates technical debt while aligning with Laravel's best practices. No business value justifies adopting this legacy sub-split."