LibSass should not import CSS files, let alone as SCSS

[nex3]

If I have two files:

// file1.scss
@import "file2";

// file2.css
$var: 12;
a {b: $var}

...LibSass will import "file2" and interpret it as SCSS rather than plain CSS. Neither of these behaviors are correct. .css files cannot be imported by Sass files without an importer, and if they could they should be interpreted as plain CSS without allowing any Sass features.

I recommend adding a deprecation warning for this as soon as possible, possibly along with a link to an example importer that will import .css files for users for whom migrating will be difficult.

[xzyfer]

This has been a long running issue, and one of the biggest node sass pain points. Thean was to removed this feature/bug with the module system landed to reduce disruption.

See #754
See #1656
See #1963

[nex3]

I'd like to at least add a warning for this as soon as possible. Dart Sass will not be implementing this behavior, so I'd like to strongly warn people away from it.

[xzyfer]

PR to add a deprecation warning #2613

[tony]

I recommend adding a deprecation warning for this as soon as possible, possibly along with a link to an example importer that will import .css files for users for whom migrating will be difficult.

Please provide some examples of how to handle importing raw CSS files from third party libraries. This would break a lot of behavior for me. It was an important feature.

[xzyfer]

It was a bug not a feature. If you want to do this your code will not be portable. If you use sassc you can use the new import extensions flag. That feature will be supported in node-sass ever.. alternatively you can use a custom importer.

…

On Sun., 29 Apr. 2018, 12:51 am Tony Narlock, ***@***.***> wrote: I recommend adding a deprecation warning for this as soon as possible, possibly along with a link to an example importer that will import .css files for users for whom migrating will be difficult. Please provide some examples of how to handle importing raw CSS files from third party libraries. This would break a lot of behavior for me. It was an important feature. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#2611 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWDIN8n7yL1GeSr0DF45fHutYZmTrks5ttIHUgaJpZM4S5TFB> .

[liamkeily]

Like @tony I was using this to import css files from an npm package, whats the best way to go about this now?

[xzyfer]

See my previous comment