sasso-rails 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 362a4798b8ebe03f26c32688f42048bc184b56a4e23a02db7d5cffbeaefcc4d8
-  data.tar.gz: 2bda2a2d286b992749ace28b314e8c86c9796bdd160d13c735a233967efc9a8d
+  metadata.gz: 182fa27772f53b3c1fbacd3befd6785adf4bac01018fb283e771e75cd4c1c53a
+  data.tar.gz: 3199c95dd402640b1408e998bf7879dd7aadcf352328e292a1e8700884be9df9
 SHA512:
-  metadata.gz: f23d4f4c8372103bf0fdaaeb86c85694eed3d861409aa99f915c580bfbde57842a811211a16f8806175db649474c9aa45421b4f4aea4266217d054dce3a32180
-  data.tar.gz: f097ec3da59d3e120408a9db2926e89d1d53d6f5b926699b7b126a7c6aa923f079f0f9d5c9ea5a342988570222bb3e34ea4043fa85660abb6254536deaa273a8
+  metadata.gz: 9b7fd563419f880c4540fa2da7a28dfcc33b06d7cc4e898ef8669794938614e0b903fcbc4e96cb365451a98890d3dcd907ca1100b7a5262f75d96a17ff767149
+  data.tar.gz: 2599b9c1c5f0e84d76b713eabbaf1bb6068863551f3d7ab38fc6b5d3ae6f1f0a6103cbc0089e00fb640a27cadd476831cfa89204ad4d5d3bf5cb169f15592130

data/CHANGELOG.md

@@ -8,6 +8,22 @@ the engine-gem version range it requires.
 
 ## [Unreleased]
 
+## [0.1.3] - 2026-06-14
+
+### Fixed
+
+- **Sprockets `assets:precompile` crash (`LoadError: cannot load such file --
+  sassc`).** On a Sprockets app (e.g. a default Rails 7.0 app), the install
+  generator left the manifest's default `//= link_directory ../stylesheets .css`
+  directive in place, so Sprockets 4 tried to COMPILE the `application.scss`
+  entrypoint with its built-in `SasscProcessor` (`require "sassc"`, not
+  installed) — harmless in dev but crashing `assets:precompile` on deploy. The
+  generator now neutralizes that directive (sasso owns the compiled output,
+  served from `../builds`, which is linked separately). Idempotent, and a no-op
+  on Propshaft (no manifest). Rails 7.0 + Sprockets now precompiles cleanly;
+  Propshaft (Rails 7.1 / 8.x) is unaffected. Verified end-to-end across both
+  pipelines, plus a generator unit test.
+
 ## [0.1.2] - 2026-06-14
 
 Requires the `sasso` gem **>= 0.2.0** (for its source-map API).

data/README.md

@@ -94,8 +94,6 @@ that directory as a source of ready-to-serve assets:
 
 ## Notes & limitations
 
-- **Source maps are not supported yet.** The in-process compiler returns CSS
-  only; there is no `.css.map` output in any environment.
 - **`builds` is file-to-file.** Each entry maps one input file to one output
   file. There is no directory-glob form (no `"." => "."`); list each entrypoint
   explicitly.
@@ -110,6 +108,29 @@ that directory as a source of ready-to-serve assets:
 - **Watch is a 1s mtime poll** (dependency-free, no native fs-events); it covers
   the source dir and `config.sasso.load_paths`.
 
+## Troubleshooting
+
+**`Bundler::GemNotFound: Could not find sasso-<version>-<platform>`** on
+`bin/rails sasso:build` (or any boot) right after `bundle install`. The `sasso`
+compiler ships as a **precompiled native gem**, so the lockfile must list your
+platform. If Bundler resolved the version but didn't materialize the native
+build for your arch, add the platform and re-install:
+
+```console
+$ bundle lock --add-platform arm64-darwin   # or x86_64-linux, aarch64-linux, etc.
+$ bundle install
+```
+
+This is a generic Bundler behaviour for precompiled native gems (the same step
+`nokogiri` etc. need on CI/Docker), not specific to sasso — but you may hit it
+on a first local install. To bake every supported platform into the lockfile up
+front:
+
+```console
+$ bundle lock --add-platform x86_64-linux aarch64-linux \
+    x86_64-linux-musl aarch64-linux-musl arm64-darwin x86_64-darwin x64-mingw-ucrt
+```
+
 ## Versioning
 
 This gem versions independently of the `sasso` compiler gem and pins it with a

data/lib/generators/sasso/install/install_generator.rb

@@ -55,9 +55,24 @@ module Sasso
         manifest = "app/assets/config/manifest.js"
         full = File.join(destination_root, manifest)
         return unless File.exist?(full)
-        return if File.read(full).include?("link_tree ../builds")
 
-        append_to_file manifest, %(//= link_tree ../builds\n)
+        unless File.read(full).include?("link_tree ../builds")
+          append_to_file manifest, %(//= link_tree ../builds\n)
+        end
+
+        # The default Sprockets manifest links the stylesheets SOURCE directory
+        # (`//= link_directory ../stylesheets .css`). Sprockets 4 then tries to
+        # COMPILE our `application.scss` entrypoint with its built-in
+        # SasscProcessor, which `require "sassc"` — not installed on a default
+        # app — so `assets:precompile` crashes with
+        # `LoadError: cannot load such file -- sassc`. sasso owns the compiled
+        # output (served from ../builds, linked above), so the raw source dir
+        # must NOT be linked. Neutralize the directive — idempotent, since the
+        # regex only matches the live `//=` form (a re-run is a no-op).
+        gsub_file manifest,
+                  %r{^([ \t]*)//=([ \t]*link_directory[ \t]+\.\./stylesheets\b.*)$},
+                  "\\1//\\2  -- disabled by sasso-rails (sasso compiles ../stylesheets to ../builds; " \
+                  "linking the source dir makes Sprockets compile .scss via sassc)"
       end
 
       def add_watch_to_procfile

data/lib/sasso/rails/version.rb

@@ -5,6 +5,6 @@ module Sasso
     # Versioned INDEPENDENTLY of both the `sasso` gem and the `sasso` crate.
     # The gemspec pins the engine gem with a range (sasso >= 0.1.1, < 1), so a
     # compiler bump does not force a lockstep release of this integration gem.
-    VERSION = "0.1.2"
+    VERSION = "0.1.3"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sasso-rails
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - momiji-rs