You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
Are importer and functions still considered experimental in libsass as noted in the documentation? I can't find a reference to their stability in the libsass documentation.
I'm not sure the versions are relevant here, but as the issue requirements asks for them:
NPM version (npm -v): 4.2.0
Node version (node -v): v7.8.0
Node Process (node -p process.versions):
Node Platform (node -p process.platform): darwin
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"): 3.13.1
This is big step towards removing non-standard raw css imports.
Using `sass_option_push_import_extension` implementors can choose
to treat any extension they like as a `.scss` file.
Closessass#1964
jiongle1
pushed a commit
to scantist-ossops-m2/node-sass
that referenced
this issue
Apr 7, 2024
This is big step towards removing non-standard raw css imports.
Using `sass_option_push_import_extension` implementors can choose
to treat any extension they like as a `.scss` file.
Closessass#1964
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Are
importer
andfunctions
still considered experimental in libsass as noted in the documentation? I can't find a reference to their stability in the libsass documentation.I'm not sure the versions are relevant here, but as the issue requirements asks for them:
npm -v
): 4.2.0node -v
): v7.8.0node -p process.versions
):node -p process.platform
): darwinnode -p process.arch
): x64node -p "require('node-sass').info"
): 3.13.1npm ls node-sass
): [email protected]The text was updated successfully, but these errors were encountered: