Statamic Sourcestack Laravel Package

Product Decisions This Supports

• Feature and DX prioritization: This release is primarily documentation and ergonomics, not a capability shift. It improves onboarding for Blade @once/@stack usage, supports adding multiple files at once, and allows pipe-separated sources to match familiar Vite-style syntax.
• Build vs. buy/adopt: For Laravel teams with Blade-heavy views and repeated asset-inclusion patterns, this package can replace small custom Blade directives or ad hoc stack logic. It is most defensible as a thin utility, not as a replacement for a full asset pipeline.
• Roadmap fit: Good candidate for a limited pilot in internal/admin UI or content-heavy Blade pages where duplicate includes and stack management are common. Avoid making it a platform-wide standard until API stability, test coverage, and Laravel-version support are confirmed.
• Use cases: Including the same script/style once across multiple components, pushing assets into Blade stacks, passing multiple entry files in one directive, and aligning Blade asset declarations with Vite-oriented team conventions.
• Release risk: v1.0.1 contains no indicated breaking changes. The whitespace-trimming fix reduces filename typo/formatting failures; pipe-separated sources improve developer experience. Overall risk is low, but the package still appears early in maturity.

When to Consider This Package

Consider it when:

• The application is Laravel/Blade-centric and has recurring asset-inclusion duplication.
• Teams already use @once and @stack patterns and want a cleaner, documented abstraction.
• Developers expect Vite-like multiple-source syntax and want to avoid custom parsing code.
• You need a small, low-ceremony utility rather than a full asset management system.
• A pilot can be scoped to non-critical views with easy rollback.

Look elsewhere when:

• You need advanced asset features such as CSP nonces, SSR integration, complex dependency graphs, CDN/versioning policies, or framework-agnostic frontend support.
• The package lacks clear Laravel version support, automated tests, or active maintenance.
• Your team already has a stable internal Blade directive or component convention that covers the same use cases.
• The asset pipeline is owned by a dedicated frontend/build system and Blade-level inclusion logic should remain minimal.

How to Pitch It (Stakeholders)

Executives: This is a low-risk Laravel utility release that reduces custom Blade glue code and improves developer ergonomics. The update is documentation and minor input-handling improvements, with no indicated breaking changes. It is worth a small pilot where Blade asset duplication is a pain point, but not yet a platform-wide mandate.

Engineering: v1.0.1 improves readability around @once/@stack, supports multiple files at once, accepts pipe-separated sources to align with Vite-style usage, and trims whitespace from filenames. These are DX and correctness improvements rather than architectural changes. Trial it in one Blade area, verify Laravel-version compatibility and test coverage, and keep rollback simple.