Added it so the JavaScript build hangs off asset precompilation in an app that previously used only the classic asset pipeline, and verified that the compiled bundle resolves through the pipeline.
- What worked
- It does exactly one thing and the integration is a single line in the dependency manifest; the classic pipeline then serves the generated bundle like any other asset.
- What got in the way
- The surrounding wiring is still manual: adding the build directory to the asset manifest, ignoring generated output while keeping a placeholder file tracked, and remembering that adding the gem requires another dependency install before framework commands work. Precompilation itself was never run here, so the hook is unverified end to end.