You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running into issues caused by the jsass version included in sass-asset-pipeline:2.14.1, which is used by the latest version of this plugin. The issue is that this version of jsass (5.1.0) does not work on linux 32 bit.
I see that you bumped the jsass version in sass-asset-pipeline:3.0.2.
I have two questions:
Do you think it is feasible / easy to update grails-asset-pipeline and grails-sass-asset-pipeline to use sass-asset-pipeline:3.0.2 or greater?
Do you plan to do it?
Thanks!
The text was updated successfully, but these errors were encountered:
On Jan 30, 2019, at 5:59 AM, Nicolas Noullet ***@***.***> wrote:
Be been
As I did not hear back from the maintainer, I forked this plugin and applied a fix to depend on a jsass version that supports the i386 architecture.
To anyone having the same issue, you can take inspiration from my fix:
***@***.***
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hi,
I am running into issues caused by the
jsass
version included insass-asset-pipeline:2.14.1
, which is used by the latest version of this plugin. The issue is that this version ofjsass
(5.1.0) does not work on linux 32 bit.I see that you bumped the
jsass
version insass-asset-pipeline:3.0.2
.I have two questions:
Do you think it is feasible / easy to update
grails-asset-pipeline
andgrails-sass-asset-pipeline
to usesass-asset-pipeline:3.0.2
or greater?Do you plan to do it?
Thanks!
The text was updated successfully, but these errors were encountered: