Weave Code
Sass Bundle Laravel Package
symfonycasts/sass-bundle
A Symfony bundle that compiles Sass/SCSS to CSS using Dart Sass and integrates with AssetMapper. It provides build and watch commands, source maps, and simple configuration for modern asset pipelines.
Delightful Sass Support for Symfony + AssetMapper
Frequently asked questions about Sass Bundle
- Can I install symfonycasts/sass-bundle in a Laravel application?
- No. symfonycasts/sass-bundle is a Symfony bundle that depends on Symfony's kernel, DI extension, AssetMapper, ImportMap, and Symfony console wiring. There is no Laravel service provider, config publishing, or Blade or Vite bridge, so a direct composer require is not feasible in a Laravel app.
- What does symfonycasts/sass-bundle actually do?
- It adds Sass and SCSS compilation to Symfony without requiring Node.js, npm, or Webpack. The bundle plugs into Symfony's AssetMapper asset system and compiles .scss and .sass sources into plain CSS, so you can use variables, nesting, mixins, and partials in a normal Symfony workflow. Configuration lives in bundle YAML so source and output paths stay version-controlled.
- Does symfonycasts/sass-bundle require Node.js or npm?
- No. The bundle is built around compiling Sass in PHP, and the evaluation notes it uses the scssphp compiler family rather than shelling out to dart-sass. Its main architectural selling point is deleting Node from the asset pipeline. You still need Composer and a Symfony app, but there is no npm install or Webpack step.
- How does SassBundle integrate with Symfony AssetMapper?
- It registers a Symfony DI extension and config tree, hooks into the AssetMapper pipeline, and compiles .scss files as part of Symfony asset tooling. It provides build and watch commands plus source maps, and it expects Symfony console wiring. That tight coupling is exactly why the bundle cannot be dropped into Laravel.
- How do I compile SCSS to CSS in Laravel without Node.js?
- Use scssphp/scssphp directly and own a small amount of glue. Add the compiler, write an artisan sass:build command plus a service provider, compile at deploy or first boot into public/build, hash the output, and point Blade at a manifest. The evaluation estimates roughly 200 to 500 lines of glue with tests. You are not installing SassBundle; you are reimplementing its no-Node pattern.
- Does scssphp support @use, @forward, and built-in Sass modules?
- Not reliably at every version. The evaluation warns that scssphp has historically lagged dart-sass on the module system, including @use and @forward, sass:math and sass:map built-in modules, newer CSS features, and edge-case output fidelity. Check your pinned scssphp version against every feature in your stylesheet graph before committing. Also test custom importers and any node_modules or pkg: resolution style you rely on.
- Is a PHP-based Sass compiler production-ready compared with dart-sass and Vite?
- It can be, but the risk profile is different. Compiler parity gaps can become either hard build failures or silent visual regressions, which is worse than a loud failure. The no-Node case is narrow and usually motivated by security scanning surface, image size, or a PHP-only platform team. If your incumbent Laravel plus Vite plus npm-installed dart-sass pipeline is well understood and CI-cached, the default recommendation is not to adopt.
- How should I test a Laravel Sass build that uses scssphp?
- Freeze your dart-sass version and generate golden-file CSS output for every entrypoint, then commit those files as fixtures. Run both compilers in CI and diff normalized output so parity gaps show up as test failures rather than production surprises. Inventory all .scss and .sass files first, cataloging @use, @forward, mixins, functions, custom importers, and package resolution. That gives you a concrete failure contract instead of relying on undocumented compiler behavior.
- Is symfonycasts/sass-bundle actively maintained and what license does it use?
- The license is MIT, which is clean for most teams. Maturity signals are modest: the evaluation cites 44 stars, a composite score of 17.4, and single-vendor authorship by SymfonyCasts. The latest tag on 2026-05-18 is recent, but one recent release does not establish a release cadence, a deprecation policy, or a multi-maintainer bus factor. Also run composer audit because the transitive scssphp dependency tree still needs supply-chain coverage.
- What are the best alternatives to symfonycasts/sass-bundle for Laravel?
- The realistic options are to keep Laravel plus Vite plus dart-sass, or to vendor the pattern with scssphp/scssphp and a custom artisan command and service provider. Use SassBundle verbatim only inside a Symfony service that already runs AssetMapper, where you gain the benefit without owning glue. Track for a Laravel-native adapter and re-evaluate in two quarters, but do not adopt the bundle directly in Laravel.
Weaver
How can I help you explore Laravel packages today?