Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Custom Functions Experimental #1964

Closed
Pezmc opened this issue May 8, 2017 · 1 comment
Closed

Custom Functions Experimental #1964

Pezmc opened this issue May 8, 2017 · 1 comment

Comments

@Pezmc
Copy link

Pezmc commented May 8, 2017

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
  • npm node-sass versions (npm ls node-sass): [email protected]
@saper
Copy link
Member

saper commented Oct 18, 2019

Yes, those are still experimental features - the current interface is subject to change.

@saper saper closed this as completed Oct 18, 2019
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.

Closes sass#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.

Closes sass#1964
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants