Bootstrap Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for the asset pipeline. This bundle replaces a hand-rolled Node/npm SCSS + purge step with three Symfony console commands (bootstrap:init, bootstrap:compile, bootstrap:purge). The PM decision: keep CSS tooling inside the PHP app lifecycle (CI, deploy hooks, container builds) instead of maintaining a parallel front-end toolchain.
• Theming and design-system roadmap. If the roadmap includes white-labeling, multi-brand or tenant-specific styling, or an admin theme layer built on Bootstrap, this package is the mechanism for SCSS-variable-level theming rather than CSS override hacks.
• Vendor-risk and TCO decisions. The 1.0.5 release adds a full PHPUnit suite, GitHub Actions CI, PHPStan, ECS, Rector and Codecov. That converts a previously "adopt at your own risk" dependency into one you can defend as adopt and depend rather than fork and internally maintain — a materially lower ongoing engineering cost line.
• Platform upgrade planning. Explicit targeting of PHP 8.2+ and Symfony 7.4 gives a concrete compatibility floor for the next framework-upgrade cycle; useful input to the upgrade budget and sequencing.
• Onboarding and DX cost. Refined commands, clearer console output, earlier and more explicit failure modes, plus expanded documentation (including a German README and developer guides) reduce ramp-up time for new engineers and cut support/debug toil.
• Adoption confidence for a 1.x dependency. Backward-compatible with a hardening-only changelog means no migration work item is needed on the roadmap.

When to Consider This Package

Consider it when:

• The application is a Symfony app on PHP 8.2+ / Symfony 7.4; this is a Symfony bundle, not a Laravel package, and there is no first-party Laravel service provider.
• You are committed to Bootstrap and want SCSS-level customization (variables, maps, partials) rather than shipping precompiled CSS with overrides.
• You want SCSS compilation and CSS purging to run as part of the PHP deploy/CI pipeline — no Node runtime, no separate front-end build image.
• You value diagnosability: 1.0.5 makes commands fail early and clearly on bad input, unreadable/unwritable files, or missing dependencies.
• You need a dependency with verifiable quality gates (tests, static analysis, coding standards, coverage reporting) for procurement or architecture review.

Look elsewhere when:

• The stack is Laravel-first. You would be writing and owning glue code; an equivalent Laravel-native asset pipeline or Vite-based approach is a better fit for the same decision.
• You already run Vite/Webpack with a mature SCSS + purge pipeline. Adopting this duplicates the build path and creates two sources of truth.
• The design system is Tailwind or CSS-in-JS, or Bootstrap is not the chosen UI foundation.
• You require long-term support on older Symfony or PHP versions; this release deliberately drops legacy complexity in favor of modern targets. Confirm an older maintenance branch exists before committing.
• You only need a prebuilt Bootstrap CSS file — the compile/purge machinery is unnecessary overhead.

How to Pitch It (Stakeholders)

For executives — one paragraph: This is a low-risk, backward-compatible maintenance release of a Bootstrap asset-compilation bundle. Nothing changes in how teams use it day to day, and there is no migration cost. What changes is the risk profile: the project now has automated tests, continuous integration, static analysis and coverage reporting, so defects get caught before they reach us and future changes are cheaper and safer to absorb. Recommendation: keep it in the stack, pin to ^1.0.5, and treat the theming pipeline as a supported dependency rather than something we might have to take in-house. Net effect is reduced total cost of ownership and a firmer compatibility baseline for our PHP 8.2 / Symfony 7.4 upgrade path.

For engineering leads:

• Stability: comprehensive PHPUnit coverage across all commands and services, including edge cases, error handling and expected output.
• Architecture: SCSS compilation and CSS purging refactored behind dedicated factory classes — cleaner dependency wiring and better error reporting when dependencies are missing.
• Failure modes: commands now fail earlier and with clearer messages on invalid input, unreadable/unwritable files and absent dependencies; console output is more predictable with better defaults.
• Tooling: Docker-based dev environment, GitHub Actions CI, PHPStan, ECS, Rector, Codecov; dev dependencies isolated via composer-bin-plugin so the production dependency tree stays lean.
• Compatibility: backward compatible. Targets Symfony 7.4 and PHP 8.2+ explicitly.
• Open checks before adoption: confirm this is the only SCSS build path in the repo (avoid duplication with Vite), and confirm the Symfony-not-Laravel constraint is understood by whoever scoped the work.