chore(deps): update dependency stylelint to v14

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
stylelint (source)	13.13.1 -> 14.1.0

---

Release Notes

stylelint/stylelint

v14.1.0

Compare Source

• Added: support for directory creation to --output-file flag (#​5672).
• Added: ConfigurationError type (#​5696).
• Added: rule-selector-property-disallowed-list rule (#​5679).
• Added: ignore: ["consecutive-duplicates-with-same-prefixless-values"] to declaration-block-no-duplicate-properties (#​5609).
• Added: ignorePseudoClasses: [] to max-nesting-depth (#​5620).
• Fixed: extending rules within overrides (#​5683).
• Fixed: color-function-notation false positives for hex colours (#​5650).
• Fixed: declaration-empty-line-before false positives for values wrapped in parentheses (#​5680).
• Fixed: indentation TypeError for baseIndentLevel: 1 option for Vue files (#​5657).
• Fixed: property-no-unknown false positives for maps (#​5690).
• Fixed: selector-type-case false positives for SVG type selectors (#​5717).

v14.0.1

Compare Source

• Fixed: package size by excluding docs (#​5643).
• Fixed: overrides property ignoring dot directories (#​5629).
• Fixed: custom syntax require error handling (#​5635).
• Fixed: function-calc-no-unspaced-operator false positives for hyphenated functions (#​5636).

v14.0.0

Compare Source

Migrating to 14.0.0 guide.

• Removed: Node.js 10 support (#​5303).
• Removed: syntax option (#​5297).
• Removed: configOverrides option (#​5530).
• Removed: rules deprecated in 13.7.0 (#​5295).
• Removed: function-calc-no-invalid rule (#​5296).
• Changed: ignoreFiles to be extendable (#​5596).
• Security: addressed ReDoS issue with regex in indentation (#​5539).
• Added: TypeScript type definitions (#​5582).
• Added: customSyntax option as a property in the configuration object (#​5538).
• Added: overrides property to configuration object (#​5521).
• Added: disableFix as secondary option to rules property in the configuration object (#​5460).
• Added: quiet option to Node.js API (#​5542).
• Added: color-hex-alpha rule (#​5316).
• Added: custom-property-no-missing-var-function rule (#​5317).
• Added: function-calc-no-unspaced-operator autofix (#​5273).
• Added: ignoreFunctions: [] to length-zero-no-unit (#​5314).
• Added: ignoreAtRules: [] to no-invalid-position-at-import (#​5520).
• Added: ignoreProperties: [] to number-max-precision (#​5421).
• Fixed: "No files matching the pattern" when using backslash paths on Windows (#​5386).
• Fixed: function-url-quotes problem messages to be consistent with other *-quotes rules (#​5488).
• Fixed: length-zero-no-unit false positives for flex property (#​5315).
• Fixed: media-feature-name-no-unknown false positives for prefers-contrast (#​5428).
• Fixed: media-feature-name-no-unknown false positives for dynamic-range & video-dynamic-range (#​5613).
• Fixed: media-feature-name-value-allowed-list TypeError for spaceless condition (#​5581).
• Fixed: property-no-unknown false positives for Less maps (#​5381).
• Fixed: selector-class-pattern false positives for Less parametric mixins (#​5378).
• Fixed: max-empty-lines autofix for Less comments (#​5507).
• Fixed: named-grid-areas-no-invalid false negatives for grid and grid-template shorthand properties (#​5514).
• Fixed: unit-no-unknown false positives for nested property declarations (#​5500).

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[pull-request-quantifier-deprecated]

This PR has 358 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Large
Size       : +57 -301
Percentile : 75.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.yaml : +56 -300

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.