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
We move a project that uses SASS and we starting to have some deprecated warning in our CSS/SASS file while running unit tests. Actually using "sass": "^1.81.0". Then it seems a breaking change is going to happen.
Deprecation Warning: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
More info: https://sass-lang.com/d/legacy-js-api
So we would like to know if a move from your side will be done, to update the project for SASS v2 (actually "sass": "^1.58.3") or we need to abandon this artefact because it won't be maintain anymore.
In our case, we decide to not go with it at the first step. We use the unstyled mode, hybrid: https://primevue.org/theming/unstyled/ then we are writing our own style.
The choice depends more on the knowledge of the dev., how they are confortable with and the current state of the project (and of course the budget). In our case, we decided to refactor our CSS/SCSS to make a deep clean as it was pretty difficult to maintain, slow in rendering and have other integration challenges.
We move a project that uses SASS and we starting to have some deprecated warning in our CSS/SASS file while running unit tests. Actually using "sass": "^1.81.0". Then it seems a breaking change is going to happen.
On the Net we caught a discussion about a v4 but the thread is relatively old... on Sep 13, 2023.
So we would like to know if a move from your side will be done, to update the project for SASS v2 (actually "sass": "^1.58.3") or we need to abandon this artefact because it won't be maintain anymore.
Also related to @import vs @use
Thank you very much for your answer.
Best regards,
The text was updated successfully, but these errors were encountered: