PHPackages                             shyim/sasso-shopware-compiler - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. shyim/sasso-shopware-compiler

ActiveSymfony-bundle

shyim/sasso-shopware-compiler
=============================

Compiles the Shopware storefront theme SCSS with the native sasso extension instead of scssphp

0.3.0(today)011↑2627.3%MITPHPPHP >=8.2

Since Jul 30Pushed today1 watchersCompare

[ Source](https://github.com/shyim/ShyimSassoCompiler)[ Packagist](https://packagist.org/packages/shyim/sasso-shopware-compiler)[ RSS](/packages/shyim-sasso-shopware-compiler/feed)WikiDiscussions main Synced today

READMEChangelog (3)Dependencies (5)Versions (4)Used By (0)

ShyimSassoCompiler
==================

[](#shyimsassocompiler)

Compiles the Shopware storefront theme SCSS with [sasso](https://crates.io/crates/sasso) — a pure-Rust dart-sass alternative — instead of `scssphp`, by decorating `Shopware\Storefront\Theme\ScssPhpCompiler`.

Uses the `shyim/sasso-ffi` package, which talks to the native library through `ext-ffi`; no PHP extension has to be compiled.

Install
-------

[](#install)

This is a plain Symfony bundle, not a Shopware plugin — there is no install/activate step and no database record, so it also works on setups where plugin management is locked down.

```
composer require shyim/sasso-shopware-compiler
```

If your project uses [Symfony Flex](https://github.com/symfony/flex), that is all — Flex detects the bundle and writes it into `config/bundles.php` itself. Shopware projects are not Flex apps by default, so register it manually:

```
// config/bundles.php
return [
    // …
    Shyim\SassoCompiler\SassoCompilerBundle::class => ['all' => true],
];
```

Clear the cache and the next `bin/console theme:compile` goes through sasso. Position in the list does not matter — service decoration is resolved after every bundle has registered.

To go back to `scssphp`, remove the line from `config/bundles.php`.

Why
---

[](#why)

`scssphp` is unmaintained upstream and is the slowest part of a theme build. On this repository's default Storefront theme:

CompilerTimeOutputscssphp1.145s349,630 bytessasso0.116s353,613 bytesRoughly a **10x** speedup for the SCSS compile step.

Output differences
------------------

[](#output-differences)

The CSS is semantically identical; where the bytes differ, sasso follows current dart-sass and `scssphp` is the outlier:

- `.5rem` instead of `0.5rem` (leading zero dropped)
- `[data-x^=bottom]` instead of `[data-x^="bottom"]` (unquoted attribute values)
- `rgba(0,0,0,0)` instead of `transparent`
- a UTF-8 BOM instead of an `@charset "UTF-8"` rule in compressed output
- `/*! … */` banner comments are stripped
- rules emitted by media-query mixins (Bootstrap's RFS) are split into separate blocks, and some selector lists are ordered differently — the resulting cascade is the same

`SCSSValidator` behaviour matches `scssphp` exactly, including which values throw.

Import resolution
-----------------

[](#import-resolution)

Shopware puts both plain directories *and* resolver closures into the compiler's `importPaths`configuration — `ThemeCompiler::getResolveImportPathsCallback()` maps `~bundle/...` urls onto absolute paths. `scssphp` accepts callables as import paths directly; sasso separates the two, so directories go to `setImportPaths()` and the closures are adapted onto sasso's two-phase importer protocol by `CallbackImporter`.

Validate
--------

[](#validate)

```
php bin/console theme:compile --sync
```

###  Health Score

40

—

FairBetter than 86% of packages

Maintenance100

Actively maintained with recent releases

Popularity7

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity38

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

3

Last Release

0d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/7c45ef9077b73fce78afbfab2fa27e611a453dd77de003e2785ac84105d02bef?d=identicon)[shyim](/maintainers/shyim)

---

Top Contributors

[![shyim](https://avatars.githubusercontent.com/u/6224096?v=4)](https://github.com/shyim "shyim (3 commits)")

### Embed Badge

![Health badge](/badges/shyim-sasso-shopware-compiler/health.svg)

```
[![Health](https://phpackages.com/badges/shyim-sasso-shopware-compiler/health.svg)](https://phpackages.com/packages/shyim-sasso-shopware-compiler)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)