Manager Laravel Package

Product Decisions This Supports

• Legacy maintenance only: If your product is a PHP application already committed to Puli for asset/package resolution, this package supports maintaining and programmatically editing the puli.json manifest rather than hand-editing configuration.
• Migration planning: Use it as an inventory/automation aid when auditing or migrating an existing Puli-based project to Composer/npm/Webpack-style tooling; it can help normalize or inspect manifest state during migration.
• Build vs buy: Buy is only defensible for short-lived legacy support; for new capabilities, build a small internal manifest editor or adopt Composer/asset tooling. This is not a strategic dependency for roadmap investment.
• Feature/use cases: CLI tooling or admin workflows that need to read/write Puli package and binding configuration, especially where multiple teams manage shared PHP assets. It does not justify new product features and should not be positioned as a differentiator.

When to Consider This Package

• You have an existing Puli-based PHP project with puli.json files that must be edited programmatically, and rewriting the editing logic would cost more than wrapping this package.
• You need a narrow, short-term internal tool to validate or mutate Puli manifests during a migration or maintenance window.
• You are comfortable with a 2016-era dependency, MIT licensing, and limited community support; you can vendor/patch it if needed.
• Look elsewhere for new projects, Laravel applications without Puli, asset pipeline management, package discovery, or any requirement for active security maintenance. The package is not Laravel-specific, has low adoption, and its last release was January 2016—treat it as unmaintained. Prefer Composer plugins, Laravel package discovery, or modern asset build tools.

How to Pitch It (Stakeholders)

Executive summary: puli/manager is a small, MIT-licensed PHP utility for managing the puli.json file in Puli projects. It is not a strategic platform component: adoption is low, it is not Laravel-specific, and it has not been released since 2016. Recommendation: do not adopt for new products or roadmap work. Approve only as a contained legacy-maintenance dependency where an existing Puli project cannot yet be migrated. Engineering should timebox any use, vendor the package, and pair it with a migration plan to standard Composer/asset tooling. The business value is risk reduction and reduced migration effort—not new capability or differentiation.