Bug: Accordion component SASS fails to compile with Angular about design-system

[laurensuh]

Hi 👋 @sfbrafkind thanks for submitting this issue. We will look into this and update you as soon as we can. Cheers!

[Dottenpixel]

@gbutt-tr @sfbrafkind thanks! Try and install an older Sass version to see if this clears the error for you npm install [email protected] --save-dev.

This is the version in the lock file. I've just recently encountered this error as well and also had 1.49.x installed in node_modules. There is a coming update in the package.json that sets the sass to 1.35.2 rather than ^1.35.2.

[gbutt-tr]

@Dottenpixel thanks this worked like a charm.

[sfbrafkind]

There is a coming update in the package.json that sets the sass to 1.35.2 rather than ^1.35.2.

Instead of restricting the version, wouldn't it be better to fix the expression by moving the multiplication inside the curly braces?

[gbutt-tr]

I am running into the exact same issue with the exact same dependencies as specified by andrewvasilchuk. Does anyone have a good workaround?

[Dottenpixel]

@sfbrafkind @gbutt-tr what version of sass is being installed into your node_modules when you run npm install?

[Dottenpixel]

@sfbrafkind @gbutt-tr what version of sass is being installed into your node_modules when you run npm install?

[gbutt-tr]

@Dottenpixel I use sass 1.49.9 in package.json, but I am seeing 1.49.11 in package-lock.json.
sass version 1.49.11 in node_modules

[sfbrafkind]

Sass v1.49.0

[Dottenpixel]

@sfbrafkind not at the moment, unfortunately. We have some downstream consumers of the Sass files that we deal with that would need to be updated first. When that work is done, we'll look to update the sass version in the project here too.

[Dottenpixel]

@sfbrafkind not at the moment, unfortunately. We have some downstream consumers of the Sass files that we deal with that would need to be updated first. When that work is done, we'll look to update the sass version in the project here too.

[Dottenpixel]

Thank you @sfbrafkind @gbutt-tr for bringing this problem to light. I'm closing this issue as the Sass version change looks to be the fix. I'll look to prioritize the sass version restriction we've made internally for release here.