Closed bodnarbm closed 3 years ago
@bolandrm, when you have a chance, I would love to know if this is something that you think should move forward in sassc-rails.
@bolandrm I tested this fix (and PR #136) inside my engine and it does indeed solve the problem.
If a processed file imported an erb asset with the erb extension in the import argument, these files would not be preprocessed by the sassc-rails and the native sassc functions would fail to compile the assets.
This change checks if the import argument ends with any of the extensions known by the sassc preprocessor, and if it does, applies the appropriate preprocessing to that file.
Addresses #123 second issue