Filament Static Assets Laravel Package

Product Decisions This Supports

• Build vs. buy (or build vs. adopt): This package is a narrow operational utility—it publishes Filament's CSS/JS into /public so the web server (nginx/Apache/CDN) serves them directly instead of routing asset requests through Laravel. It informs the decision of whether to depend on a package for this or simply add a cp/publish step to the deploy pipeline. In most cases the "build" side is a 5-line deploy script, which is the key trade-off to weigh.
• Performance and infrastructure roadmap: Supports initiatives like reducing PHP-FPM load, enabling long-lived cache headers, offloading admin panel assets to a CDN, and supporting immutable/build-time asset deployment.
• Deployment-target flexibility: Directly relevant if the product must run on shared hosting, behind restrictive WAF/proxy rules, or in environments where Filament's asset routes are blocked or misconfigured (common with reverse proxies and APP_URL mismatches).
• Version pinning and upgrade planning: Because the last release is from March 2023 and targets an older Filament asset-serving behavior, adopting it forces a decision about which Filament version the product standardizes on—or whether the need disappears on newer Filament releases.
• Not a differentiator: This is plumbing. It should be evaluated as a maintenance-line item in the backlog, not as a roadmap feature.

When to Consider This Package

Consider it when:

• The admin panel (Filament) is a production-critical surface and asset delivery latency or PHP overhead is a measurable problem.
• The deployment target cannot or should not route static files through Laravel (shared hosting, locked-down environments, CDN-first architectures).
• You already run an artisan command during deploy and adding one more step is trivial.
• You need a stopgap now and can accept a small, unmaintained dependency.

Look elsewhere (or skip it) when:

• You are on a Filament version where asset publishing/serving is handled natively—verify this first, as the package's 2023 release predates several Filament changes.
• You require active maintenance, security patching, or vendor support. With 15 stars and no release in over two years, treat it as unmaintained.
• Your build pipeline can copy vendor/filament/*/dist to public/ directly—this achieves the same outcome with zero dependency risk. This is likely the better default.
• You need a documented API or SLA for a regulated or enterprise environment.

How to Pitch It (Stakeholders)

To executives: This is a small, free (MIT), single-purpose utility that lets our admin panel's static files be served by the web server or CDN rather than by PHP. It has a plausible but modest performance and deployment-flexibility upside. It carries no licensing cost and no vendor lock-in—it can be removed without touching application code. The material risk is that it has not been updated since early 2023 and has minimal community adoption, so I would not position it as a strategic dependency. Recommendation: a short, timeboxed spike to confirm whether we need it at all, since our build pipeline may already give us the same result with a one-line copy step.

To engineering: This collapses to "publish Filament assets to /public and let nginx/CDN handle them." Before adopting, confirm (a) which Filament version we're on and whether it already supports this, and (b) whether a deploy-script copy is equivalent. If we adopt, isolate it—keep the asset path configurable and document the manual fallback so we can drop the dependency at any time. Treat the package as a convenience wrapper, not a framework commitment.