This repository has been archived by the owner on Feb 18, 2022. It is now read-only.
Export to SCSS file #212
Merged
Export to SCSS file #212
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
romainmenke
pushed a commit
to csstools/postcss-plugins
that referenced
this pull request
Dec 15, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my project, I use CSS custom properties but I also need them as SCSS variables for use with libraries that are written in SCSS that need to be customized.
This is a rather simple implementation but it does the trick.
Another thing I'd like to add would be the ability to also resolve
var()statements in values, so that--color: var(--blue);is transformed to--color: blue. That would allow us to export files that are free from custom properties, so we can have a "normal" SCSS var file, for example.However, this seems like a not so simple task...