build(deps): bump autoprefixer from 10.4.1 to 10.4.14

[dependabot]

Bumps autoprefixer from 10.4.1 to 10.4.14.

Release notes

Sourced from autoprefixer's releases.

10.4.14

• Improved startup time and reduced JS bundle size (by @​Knagis).

10.4.13

• Fixed missed prefixes on vendor prefixes in name of CSS Custom Property.

10.4.12

• Fixed support of unit-less zero angle in backgrounds (by @​yisibl).

10.4.11

• Fixed text-decoration prefixes by moving to MDN data (by @​romainmenke).

10.4.10

• Fixed unicode-bidi prefixes by moving to MDN data.

10.4.9

• Fixed css-unicode-bidi issue from latest Can I Use.

10.4.8

• Do not print color-adjust warning if print-color-adjust also is in rule.

10.4.7

• Fixed print-color-adjust support in Firefox.

10.4.6

• Fixed print-color-adjust support.

10.4.5

• Fixed NaN in grid (by @​SukkaW).

10.4.4

• Fixed package.funding to have same value between all PostCSS packages.

10.4.3

• Fixed package.funding (by @​mondeja).

10.4.2

• Fixed missed -webkit- prefix for width: stretch.

Changelog

Sourced from autoprefixer's changelog.

Commits

• db162a1 Release 10.4.14 version
• b385c2e Update dependencies
• 48010ae Improves startup time by requiring specific caniuse files (#1492) (#1493)
• c5a86ab Fix package manager info (#1489)
• 3e0ef96 Update dependencies
• e07754b Remove old CI config
• 3c6f9f1 Update dependencies
• 4782f79 update postcss to 8.4.19 (#1485)
• 1895e98 Release 10.4.13 version
• 8caf491 Update dependencies
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

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 detected.
• 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.