This repository was archived by the owner on Feb 18, 2022. It is now read-only.
8.0.1 #135
Merged
8.0.1 #135
Conversation
This file contains hidden or 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
a4e2c18 to
6270596
Compare
6270596 to
d263622
Compare
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.
Resolves #134 by working around an issue with postcss-values-parser.
I’ve PR’d a fix to postcss-values-parser which has been merged. shellscape/postcss-values-parser#55
Once postcss-values-parser publishes an update (postcss-values-parser@1.5.1) then I will bump that dependency and remove my fix in another patch release (postcss-custom-properties@8.0.2). shellscape/postcss-values-parser#56
At that point, new 8.0.0 and 8.0.2 installs will work due to the fix in postcss-values-parser, while 8.0.1 installs will work due to my workaround.
This change also adds sourcemaps to the published versions to better report future issues.