-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saas @import
is deprecated
#815
Comments
Thank you for reporting this, @martgil. However, Minima won't be switching over to the To reduce the warnings to a minimum, you may set the # _config.yml
sass:
quiet_deps: true Ideally, |
@ashmaroli PR to add new deprecation options: jekyll/jekyll-sass-converter#164 Please take a look when you get a chance. |
Thanks, @ashmaroli, for the detailed explanation, and @ntkme for creating the PR. I understand the reasoning and the decision. |
The correct way is to ask users using Jekyll 3 to write |
If I understand correctly, you are saying that neither the v2.x branch nor the v3.x branch of Minima will be updated to the new DartSass API, right? Is there any pathway to a later breaking release that is compatible with DartSass v3.x? |
@maxkapur Yes, you understood my earlier comment correctly. But I have thought about this situation over these days. |
This page from Sass documentation announced that usage of
@import
is deprecated: https://sass-lang.com/blog/import-is-deprecated.The current theme however is still using this deprecated rule. When executing
jekyll build
, the warning the deprecation of the said rule is described where the source file for sass files is not present where it is installed.I have this original Gemfile from fresh installation of jekyll project:
logs:
The text was updated successfully, but these errors were encountered: