-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
Use SASS as a template engine for CSS/SCSS files #408
Comments
@zachleat what's the opportunity on opening a plugin API for engines? If the engine API could be partially standardized, I think this could easily be done through plugins, allowing us to add less, sass, and more support. |
I see this API binding a node module to a set of file extensions. This module would basically tell eleventy how to:
|
This is exactly the thing proposed by #117. After this API becomes available, we can defer this to plugins (some first party, some third party). |
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. View the enhancement backlog here. Don’t forget to upvote the top comment with 👍! |
👍 |
It's been nearly 2 years since a comment on this thread, but just noting that if this does go ahead, be aware that In the meantime, for those looking, I found |
Hey @SimonEast, you can check out my 11ty starter that features Gulp and Dart SASS https://github.com/frontenso/frontenso-11ty-starter |
It would be good to be able to optionally use node-sass as the template renderer for .css/scss files...
It seems to similar fit the same architectural pattern as any other template engine, albeit for a different type of file...
What would be the difficulty in supporting this as an option?
Thanks :)
The text was updated successfully, but these errors were encountered: