I’m surprised more people aren’t posting about this and fourseven:scss hasn’t been updated to support v3, since it’s the recommended SCSS package.
I would have imagined a lot of projects would be affected by this change, but I suppose a lot of people aren’t updating to v3 yet since it can require a ton of work, updating all the async collection methods.
I feel like I’m in some kind of bizarro world here, and while I normally wouldn’t want to derail a conversation, I want to post here since a solution has already been posted/selected.
Just curious if anyone has any thoughts or insights! Thanks.
We’re using fourseven:scss a lot. It’s one of the reasons why we haven’t dared to update to Meteor 3.0. Not because I already knew it wouldn’t work, but because this package was a headache on many Meteor updates in the past. Which is not to blame the original author, there were just too many breaking changes in the build system, I guess. Can these other packages be used as a drop-in-replacement, or was there additional work to do?
We switched to leonardoventurini:scss@1.1.5 (for Meteor 2) and have never looked back. It has a Meteor3-compatible version that works just as well and uses the more modern dart compiler under the hood.