[Snyk] Upgrade stylelint from 9.10.1 to 16.17.0 #33
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.
Snyk has created this PR to upgrade stylelint from 9.10.1 to 16.17.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 114 versions ahead of your current version.
The recommended version was released 25 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-STYLELINT-1585622
SNYK-JS-TRIM-1017038
SNYK-JS-TRIMNEWLINES-1298042
SNYK-JS-POSTCSS-5926692
SNYK-JS-GLOBPARENT-1016905
SNYK-JS-STYLELINT-460283
SNYK-JS-YARGSPARSER-560381
Release notes
Package name: stylelint
It adds 1 new rule, support for
languageOptions
to 2 rules, 1 option to a rule, the--compute-edit-info
CLI flag (along with support forEditInfo
in 3 rules), and fixes 1 bug.EditInfo
is useful for automated fixing tools and editor integrations.layer-name-pattern
rule (#8474) (@ ryo-manba).--compute-edit-info
CLI flag (#8473) (@ ryo-manba).ignorePreludeOfAtRules: []
tolength-zero-no-unit
(#8472) (@ ryo-manba).at-rule-no-unknown
support forlanguageOptions
(#8475) (@ ryo-manba).property-no-unknown
support forlanguageOptions
(#8476) (@ ryo-manba).declaration-block-no-redundant-longhand-properties
support for computingEditInfo
(#8482) (@ pamelalozano16).function-url-quotes
support for computingEditInfo
(#8483) (@ pamelalozano16).selector-attribute-quotes
support for computingEditInfo
(#8484) (@ pamelalozano16).custom-property-pattern
false negatives for@ property
preludes (#8468) (@ rohitgs28).It adds support for computing
EditInfo
to 22 more rules and reverts a change that addedcontext.lexer
to our public API in the previous release.at-rule-empty-line-before
support for computingEditInfo
(#8425) (@ pamelalozano16).at-rule-no-deprecated
support for computingEditInfo
(#8426) (@ pamelalozano16).at-rule-no-vendor-prefix
support for computingEditInfo
(#8427) (@ pamelalozano16).color-function-notation
support for computingEditInfo
(#8437) (@ pamelalozano16).declaration-empty-line-before
support for computingEditInfo
(#8443) (@ pamelalozano16).declaration-property-value-keyword-no-deprecated
support for computingEditInfo
. (#8439) (@ pamelalozano16).font-family-name-quotes
support for computingEditInfo
(#8419) (@ ryo-manba).font-weight-notation
support for computingEditInfo
(#8420) (@ ryo-manba).function-calc-no-unspaced-operator
support for computingEditInfo
(#8440) (@ pamelalozano16).function-name-case
support for support for computingEditInfo
." (#8442) (@ pamelalozano16).hue-degree-notation
support for computingEditInfo
(#8444) (@ pamelalozano16).import-notation
support for computingEditInfo
. (#8445) (@ pamelalozano16).keyframe-selector-notation
support for computingEditInfo
(#8457) (@ pamelalozano16).length-zero-no-unit
support for computingEditInfo
(#8459) (@ pamelalozano16).lightness-notation
support for computingEditInfo
(#8458) (@ pamelalozano16).media-feature-name-no-vendor-prefix
support for computingEditInfo
(#8456) (@ pamelalozano16).media-feature-range-notation
support for computingEditInfo
(#8455) (@ pamelalozano16).property-no-vendor-prefix
support for computingEditInfo
(#8461) (@ pamelalozano16).rule-empty-line-before
support for computingEditInfo
(#8460) (@ pamelalozano16).selector-no-vendor-prefix
support forEditInfo
(#8462) (@ pamelalozano16).selector-not-notation
support for computingEditInfo
(#8463) (@ pamelalozano16).selector-pseudo-element-colon-notation
support forEditInfo
(#8464) (@ pamelalozano16).selector-type-case
support for computingEditInfo
(#8467) (@ pamelalozano16).shorthand-property-no-redundant-values
support for computingEditInfo
(#8466) (@ pamelalozano16).value-keyword-case
support for computingEditInfo
(#8469) (@ pamelalozano16).value-no-vendor-prefix
support for computingEditInfo
(#8470) (@ pamelalozano16).Could not find a declaration file for module 'css-tree'
type error (#8452) (@ danielrentz).It adds 1 new rule, a
languageOptions
configuration property for configuring some of the new rules added in16.13.0
, regex support to 1 option and support for computingEditInfo
to 6 rules. It fixes 9 bugs, including 2 with thetap
reporter.syntax-string-no-invalid
rule (#8331) (@ ryo-manba).languageOptions
configuration property (#8297) (@ ryo-manba).ignoreAtRules
option ofat-rule-empty-line-before
(#8385) (@ ryo-manba).alpha-value-notation
support for computingEditInfo
(#8369) (@ pamelalozano16).color-hex-length
support for computingEditInfo
(#8415) (@ ryo-manba).comment-empty-line-before
support for computingEditInfo
(#8416) (@ ryo-manba).comment-whitespace-inside
support for computingEditInfo
(#8417) (@ ryo-manba).custom-property-empty-line-before
support for computingEditInfo
(#8418) (@ ryo-manba).declaration-block-no-duplicate-properties
support for computingEditInfo
(#8363) (@ romainmenke).tap
formatter not escaping#
and\
in its test point descriptions (#8334) (@ Mouvedia).tap
formatter outputting invalid YAML blocks for rules containing double quotes in their warnings' messages (#8334) (@ Mouvedia).declaration-block-no-redundant-longhand-properties
false positives for properties with!important
(#8366) (@ immitsu).EditInfo
missing semicolon intext
field (#8370) (@ pamelalozano16).declaration-property-value-keyword-no-deprecated
false negatives fortext-decoration: blink
(#8351) (@ Mouvedia).declaration-property-value-keyword-no-deprecated
false positives for styled components interpolated functions (#8392) (@ Mouvedia).font-family-name-quotes
false positives due to vendor-prefixed font-size values (#8393) (@ Mouvedia).font-family-no-missing-generic-family-keyword
false positives formath
,emoji
andfangsong
(#8395) (@ ViachaslauIhnatsiuk).selector-type-no-unknown
false positives forselectmenu
andpopup
(#8376) (@ Mouvedia).It fixes a bug with caching.
It fixes 8 bugs and adds features to our
Warning
type.Warning
type (#8234) (@ romainmenke).SyntaxError: The requested module 'table'...
(#8325) (@ denisx).RuleContext['fix']
type (#8309) (@ Mouvedia).declaration-property-value-keyword-no-deprecated
autofix ofborder-color
andoverflow
(#8346) (@ Mouvedia).declaration-property-value-keyword-no-deprecated
false negatives foroverflow-x
andoverflow-y
(#8340) (@ Mouvedia).declaration-property-value-keyword-no-deprecated
false negatives forscrollbar-color
(#8346) (@ Mouvedia).declaration-property-value-keyword-no-deprecated
false positives for non-standard syntax values (#8329) (@ Mouvedia).declaration-property-value-keyword-no-deprecated
warning message foroverflow: <keyword> <keyword>
(#8340) (@ Mouvedia).selector-pseudo-class-no-unknown
false positives for:has-slotted
(#8332) (@ Mouvedia).It fixes a regression bug with
--fix
.--fix
CLI flag raising unknown value error (#8313) (@ ybiquitous).It fixes one bug due to an upstream change in our
ignore
dependency.ignore.default is not a function
(#8305) (@ romainmenke).It adds 3 rules to help you write error-free at-rules and 2 rules to warn you about deprecated CSS features. We've turned these rules on in our standard config. It also adds new rule options, a feature to display how long rules take, lax autofix and support for
messageArgs
in more rules. It fixes 7 bugs. Lastly, we've made a deprecation that may affect some plugins. We've updated our docs for plugin authors and end users on how to silence deprecation warnings.utils.report()
(#8244) (@ romainmenke).lax
/strict
values to thefix
Node.js API option and CLI flag (#8106) (@ ryo-manba).TIMING
environment variable (#8108) (@ ryo-manba).at-rule-descriptor-no-unknown
rule (#8197) (@ ryo-manba).at-rule-descriptor-value-no-unknown
rule (#8211) (@ ryo-manba).at-rule-no-deprecated
rule (#8251) (@ jeddy3).at-rule-prelude-no-invalid
rule (#8268) (@ ryo-manba).declaration-property-value-keyword-no-deprecated
rule (#8223) (@ Mouvedia)."ignore": ["at-rule-preludes", "declaration-values"]
tostring-no-newline
(#8214) (@ ryo-manba).messageArgs
todeclaration-property-value-no-unknown
,font-family-name-quotes
,font-family-no-duplicate-names
,function-calc-no-unspaced-operator
,import-notation
,media-feature-name-unit-allowed-list
,selector-attribute-quotes
andselector-pseudo-element-colon-notation
(#8285 & #8252) (@ Mouvedia).*-no-vendor-prefix
message ambiguity (#8239) (@ Mouvedia).at-rule-(dis)allowed-list
,at-rule-no-vendor-prefix
,at-rule-property-required-list
message argument (#8277) (@ Mouvedia).at-rule-property-required-list
message for inclusion of properties and descriptors (#8207) (@ jeddy3).at-rule-*
false positives and negatives for@ charset
rule (#8215) (