Skip to content

"Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0." Message #199

Description

@C0DE33301

I'm trying to view the theme but I'm getting this message

Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.
More info and automated migrator: https://sass-lang.com/d/import
  ╷
1 │ @import 'jekyll-theme-hacker';
  │         ^^^^^^^^^^^^^^^^^^^^^
  ╵
    /home/kittens/Documents/GitHub/hacker/assets/css/style.scss 1:9  root stylesheet

Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.
More info and automated migrator: https://sass-lang.com/d/import
  ╷
1 │ @import "rouge-base16-dark";
  │         ^^^^^^^^^^^^^^^^^^^
  ╵
    jekyll-theme-hacker.scss 1:9                                     @import
    /home/kittens/Documents/GitHub/hacker/assets/css/style.scss 1:9  root stylesheet

Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.
More info and automated migrator: https://sass-lang.com/d/import
  ╷
2 │ @import "default_colors";
  │         ^^^^^^^^^^^^^^^^
  ╵
    jekyll-theme-hacker.scss 2:9                                     @import
    /home/kittens/Documents/GitHub/hacker/assets/css/style.scss 1:9  root stylesheet

Deprecation Warning [import]: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.
More info and automated migrator: https://sass-lang.com/d/import
  ╷
6 │ @import "default_colors";
  │         ^^^^^^^^^^^^^^^^
  ╵

When I did a quick search about this message I get,

For years, the @import rule has been the go-to approach for handling modular Sass code. However, the Sass team announced the deprecation of @import in favor of the newer module system. 
If your build process or existing codebase shows a warning—“Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.”—it’s time to switch to the recommended @use or @forward directives.

from website

My question, is it OK to update the assets/css/style.scss file to avoid the very annoying message?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions