Replies: 4 comments 3 replies
-
we updgraded our project not too long ago and I remember this calc() deprecation error. we found this https://sass-lang.com/documentation/breaking-changes/slash-div#automatic-migration and ran those lines and it fixed that error at least. but i believe we also had issues with scss processing super slow. I will try to look back and see how we fixed it. |
Beta Was this translation helpful? Give feedback.
-
The new dart-sass ("sass": "^1.52.2") is very slow on mac M1 with node 16, 17, 18. If node is running in native arm64 code you are unable to install node-sass, so you are forced to use the newer much slower version of dart-sass which is completely written in javascript. I was hoping to speed things up with a newer native version of node. The only way to get this properly running on Mac m1 is to run node v14.19.3 which is run through Rosetta and allows you to install the faster old node-sass. Building foundation version 6.6.x (4.5 seconds) is also much faster than building foundation 6.7.x (9 seconds) (with node-sass). For me the new dart-sass is unusable as it is way too slow. Does anyone else know a faster solution? Why is foundation 6.7 slower than 6.6? |
Beta Was this translation helpful? Give feedback.
-
I am having similar issues too, and added a bug report: #12592 |
Beta Was this translation helpful? Give feedback.
-
@RVXD you could try switching to the |
Beta Was this translation helpful? Give feedback.
-
I have been testing upgrading from webpack4 to webpack5. I know I have quite many things that can slow down the build times. I am testing 3 endpoints where a full build goes from about 10 seconds to 20 seconds, watching a single scss file after that goes from 1 to about 4 seconds. I tested also change to some file that doesn't use any foundation mixin and that goes much faster.
Here are the relevant packages I am testing with:
I mostly wanted to update to get rid of these kind of warnings:
Beta Was this translation helpful? Give feedback.
All reactions