Merged
Conversation
Owner
|
Thank you! This would explain regression I saw while updating to Stylelint 16.11.0+ (version, where new utilities for reported ranges were used). I didn't feel comfortable with massive change in package-lock due to lockfile version change. So, if you can, could you rebase on |
Contributor
Author
Thank you for catching this! |
Owner
No worries :) |
Owner
|
Thank you for your help! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PostCSS 8.4.x started using
Node.source.input.cssmore and more in various methods.Mostly when calculating source positions (e.g.
positionInside,rangeBy, ...).This conflicted with how
postcss-styled-syntaxwas implemented, so we added a new field through which custom syntax plugins can provide the entire document source.This is mostly important for linters where accurate positioning in the original source files is key.
It seemed that there was no test coverage for these postcss node methods so I've added one commit with some test coverage and a second where I integrated
Input#documentand updated postcss in the lock file.