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
Support .import.scss suffix #904
Comments
Sorry, it is not official, if you need this, please open an issue in sass repo and when they implemented this we will support it too |
@alexander-akait I'm not sure what I have to ask in the sass repo. My usecase only explains the usecase. I'm not asking for you to invent something new. |
If it is in docs we are supporting this |
Thanks for clarifying that! Could this ticket be re-opened? This feature doesn't work with sass-loader at this point in time. |
I can't open it, because it works, if it doesn't work provide reproducible test repo, double check you use |
It doesn't work, that's why I opened the ticket in the first place.
I'll be happy to provide a repro
…On Tue, Dec 1, 2020, 14:54 Alexander Akait ***@***.***> wrote:
I can't open it, because it works, if it doesn't work provide reproducible
test repo, double check you use sass (dart-sass), it doesn't work on
node-sass
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#904 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGISBVM4V4M3XE7CMP325DSSTYRFANCNFSM4UHYMQRQ>
.
|
Please provide reproducible test repo and I will reopen this if we will have bug |
I've opened #905, which contains a failing test. While creating the test I noticed there's a pretty clean workaround, there's more info in the PR. |
Feature Proposal
Support loading files with the
.import.scss
extension when used with@import
Feature Use Case
As a Sass library author I can support usage of my library using
@use
and@import
by providing two files:/path/to/_file.scss
for@use
and/path/to/_file.import.scss
for@import
.The
_file.scss
uses regular names for all variables and mixins, while the_file.import.scss
exposes all of these things with a prefix to prevent name clashes.Sass doesn't pass what method is used to the importer as far as I could tell, so it doesn't look like the importer can perform this logic itself.
However, by resolving the path to
/path/to/_file
without any extensions sass itself will resolve this correctly, finding.import.scss
files when they exist.The text was updated successfully, but these errors were encountered: