Compass Mixins Laravel Package

Product Decisions This Supports

• Frontend build-pipeline modernization: whether to migrate off Ruby Sass/Compass to libsass or Dart Sass. This package is the compatibility layer that turns that migration into a build-config change rather than an SCSS rewrite.
• Legacy codebase triage: sizing the "Compass exit" workstream. If Compass mixin call sites are few, skip the dependency and codemod; if they number in the thousands, adopt this as a transitional shim and set a removal date.
• Build vs. buy: prefixing, clearfix, gradients, and typography mixins are commodity — Autoprefixer plus a small internal mixin partial covers nearly all of it. The only non-commodity value here is API compatibility with existing @include call sites. Frame the decision as "buy migration time," not "buy functionality."
• Vendor vs. dependency: last release October 2021, no discoverable repository, license declared NOASSERTION. If adopted, vendor the partials into resources/sass/vendor/ and commit them, so builds stay reproducible and the artifact is frozen at a known state.
• Registry hygiene: despite being listed among Laravel/PHP packages, this contains no PHP. Route it through frontend tooling and legal review, not the Composer dependency policy — otherwise it gets evaluated against the wrong criteria and the wrong owner.
• Roadmap signal: adoption is inherently dated. Sass @import is deprecated in Dart Sass 1.80+ and removed in 3.0, and Compass's own idiom is global imports. Any adoption decision should carry an explicit expiry tied to that deprecation.

When to Consider This Package

Adopt when:

• An existing SCSS codebase calls Compass mixins — @include border-radius, background-image, clearfix, single-transition, opacity, typography/vertical-rhythm helpers — and you need it to build without Ruby installed in CI.
• You are on Laravel Mix or Vite with node-sass/Dart Sass and want a drop-in @import that resolves those mixin names at no rewrite cost.
• The rewrite cost demonstrably exceeds the cost of carrying a frozen, unmaintained dependency for one or two release cycles.
• Legal has cleared the license in writing. Upstream Compass is MIT and this is a repackaging, so the answer is probably yes — but NOASSERTION in the manifest is a gate, not a footnote, before this ships inside a customer artifact.

Look elsewhere when:

• Greenfield work. Use Autoprefixer, Dart Sass modules (@use), and design tokens. There is no reason to import a 2021 Compass port into a new project.
• You rely on Compass's Ruby-only capabilities — sprite generation, image dimension/color functions, inline asset helpers. Pure SCSS cannot reproduce these, and this package does not try to. Use postcss-sprites, svg-sprite, or build-time asset tooling.
• There is no Sass pipeline at all (Tailwind, CSS-in-JS, plain CSS) — the dependency is simply inert.
• You need maintenance guarantees, security response, or a supported license. You get none of those here.
• The mixin surface is shallow. Most of what Compass prefixed is now native CSS; a short codemod sprint is cheaper long-term than an unowned dependency in the build graph.

How to Pitch It (Stakeholders)

Executives: This is a small, unmaintained stylesheet library that lets an existing frontend keep building while we modernize our Sass compiler. It is a bridge, not a foundation. It costs nothing, removes a Ruby toolchain from CI, and lets us migrate on our own schedule instead of under a forced rewrite. Two caveats worth knowing: the license is technically undeclared (upstream Compass is MIT, so this is very likely fine, but legal should confirm before it enters a shipped artifact), and it is a one-way door we should plan to walk back out of within two quarters. My recommendation is to vendor the files into the repository rather than take a live dependency on them.

Engineering: Drop the Compass partials into resources/sass/vendor/compass/ and @import them ahead of our own partials. Compass mixin names resolve and the compass compile step leaves the build. Expect three cleanup items: global mixin namespace collisions with our own libraries, duplicated vendor prefixes now that Autoprefixer is also in the pipeline (assign one owner for prefixing), and the fact that this is on borrowed time — Sass @import is deprecated, and Compass's Ruby-only helpers for sprites and image functions are not replaced by this package. Inventory the affected call sites now so the eventual exit is a scoped task rather than a discovery.