Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
postcss (source)	8.3.11 -> 8.4.4
prettier (source)	2.4.1 -> 2.5.0
sass	1.37.5 -> 1.44.0
svgo	2.7.0 -> 2.8.0

---

Release Notes

postcss/postcss

v8.4.4

Compare Source

• Fixed absolute path in source map on zero plugins mode.

v8.4.3

Compare Source

• Fixed this.css.replace is not a function error.

v8.4.2

Compare Source

• Fixed previous source map support in zero plugins mode.

v8.4.1

Compare Source

• Fixed Stringifier types (by James Garbutt).

v8.4.0

Compare Source

PostCSS 8.4 brought ranges for warnings and errors, smaller node_modules size, lazy parsing to avoid PostCSS does nothing warning, and TypeScript fixes.

Thanks to Sponsors

This release was possible thanks to our community.

If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:

• Tidelift with a Spotify-like subscription model supporting all projects from your lock file.
• Direct donations in PostCSS & Autoprefixer Open Collective.

Rages for Errors and Warnings

@​adalinesimonian, the author of amazing Stylelint extension for VS Code, added ranges to errors and warnings.

result.warn(msg, { index })           // One character warning at index
result.warn(msg, { endIndex })        // Starts at node start, ends at endIndex
result.warn(msg, { index, endIndex }) // Starts at index, ends at endIndex
result.warn(msg, { start })           // Starts at start, ends at node end
result.warn(msg, { end })             // Starts at node start, ends at end
result.warn(msg, { start, end })      // Starts at start, ends at end
result.warn(msg, { word })            // Starts at word location, ends at word index + length

It will improve DX in the IDE extension.

Lazy Parsing

Previously, we found that many tools run PostCSS even if the developer didn’t pass any PostCSS plugins. Parsing is the most expensive step in CSS processing. It led to a waste of resources without any reason.

We tried to resolve the problem by adding a PostCSS does nothing warning. But it didn’t force tool authors to be more careful with user’s resources.

If PostCSS sees that tool call it without passing plugins (or changing parser/stringifier), PostCSS will not parse CSS (until toll will call Result#root). In 8.4, @​bogdan0083 (with the help of @​WilhelmYakunin) tries to solve the problem in another way. It allows us to save resources and remove the PostCSS does nothing warning.

// No plugins, we do not parse CSS
let result = await postcss().process(css, { from  })
result.css  // Is the same string passed to process()
result.map  // Special 1-to-1 source map
result.root // CSS will parsed only here

Install Size Reduction

With ≈60M weekly downloads, PostCSS has responsibility for the world’s resource spending.

Together with @​7rulnik we reduced source-map-js size. It is transitive dependency of PostCSS.

In 8.4, we moved to a fixed version of source-map-js, which reduced the postcss size in your node_modules from ≈1 MB to 0.3 MB. With the huge popularity of PostCSS, it will free a lot of resources on our CIs.

#### Migration from Jest to `uvu`

@​kimoofey refactored all tests from the popular Jest framework to small and fast uvu.

It will not affect end-users. However, it reduced our node_modules size by 33 MB and made tests twice faster (yarn install & yarn unit: 24 → 13 seconds).

TypeScript Fixes

• Added Processor types.
• Added Stringifier types (by @​43081j).
• Fixed types Root and Document in result values (by @​43081j).
• Fixed Node#walkRules() types (by @​hudochenkov).

Other Changes

• Fixed docs (by @​paulshryock).

prettier/prettier

v2.5.0

Compare Source

diff

🔗 Release Notes

sass/dart-sass

v1.44.0

Compare Source

• Suggest calc() as an alternative in /-as-division deprecation messages.

Dart API

• Add SassNumber.convert() and SassNumber.convertValue(). These work like
  SassNumber.coerce() and SassNumber.coerceValue(), except they don't treat
  unitless numbers as universally compatible.

• Fix a bug where SassNumber.coerceToMatch() and
  SassNumber.coerceValueToMatch() wouldn't coerce single-unit numbers to
  match unitless numbers.

v1.43.5

Compare Source

• Fix a bug where calculations with different operators were incorrectly
  considered equal.

• Properly parse attribute selectors with empty namespaces.

JS API

• Print more detailed JS stack traces. This is mostly useful for the Sass team's
  own debugging purposes.

v1.43.4

Compare Source

JS API

• Fix a bug where the logger option was ignored for the render() function.

v1.43.3

Compare Source

• Improve performance.

v1.43.2

Compare Source

• Improve the error message when the default namespace of a @use rule is not
  a valid identifier.

v1.42.1

Compare Source

• Fix a bug where Sass variables and function calls in calculations weren't
  being resolved correctly if there was a parenthesized interpolation elsewhere
  in the file.

v1.42.0

Compare Source

• min() and max() expressions are once again parsed as calculations as long
  as they contain only syntax that's allowed in calculation expressions. To
  avoid the backwards-compatibility issues that were present in 1.40.0, they now
  allow unitless numbers to be mixed with numbers with units just like the
  global min() and max() functions. Similarly, + and - operations within
  min() and max() functions allow unitless numbers to be mixed with numbers
  with units.

v1.41.1

Compare Source

• Preserve parentheses around var() functions in calculations, because they
  could potentially be replaced with sub-expressions that might need to be
  parenthesized.

v1.41.0

Compare Source

• Calculation values can now be combined with strings using the + operator.
  This was an error in 1.40.0, but this broke stylesheets that were relying on
  $value + "" expressions to generically convert values to strings. (Note that
  the Sass team recommends the use of "#{$value}" or inspect($value) for
  that use-case.)

• The selector.unify() function now correctly returns null when one selector
  is a :host or :host-context and the other is a selector that's guaranteed
  to be within the current shadow DOM. The @extend logic has been updated
  accordingly as well.

• Fix a bug where extra whitespace in min(), max(), clamp(), and calc()
  expressions could cause bogus parse errors.

• Fix a bug where the right-hand operand of a - in a calculation could
  incorrectly be stripped of parentheses.

Dart API

• SassCalculation.plus() now allows SassString arguments.

v1.40.1

Compare Source

• Potentially breaking bug fix: min() and max() expressions outside of
  calculations now behave the same way they did in 1.39.2, returning unquoted
  strings if they contain no Sass-specific features and calling the global
  min() and max() functions otherwise. Within calculations, they continue to
  behave how they did in 1.40.0.

  This fixes an unintended breaking change added in 1.40.0, wherein passing a
  unitless number and a number without units to min() or max() now produces
  an error. Since this breakage affects a major Sass library, we're temporarily
  reverting support for min() and max() calculations while we work on
  designing a longer-term fix.

v1.40.0

Compare Source

• Add support for first-class calc() expressions (as well as clamp() and
  plain-CSS min() and max()). This means:

  • calc() expressions will be parsed more thoroughly, and errors will be
    highlighted where they weren't before. This may break your stylesheets,
    but only if they were already producing broken CSS.

  • calc() expressions will be simplified where possible, and may even return
    numbers if they can be simplified away entirely.

  • calc() expressions that can't be simplified to numbers return a new data
    type known as "calculations".

  • Sass variables and functions can now be used in calc() expressions.

  • New functions meta.calc-name() and meta.calc-args() can now inspect
    calculations.

Dart API

• Add a new value type, SassCalculation, that represents calculations.

• Add new CalculationOperation, CalculationOperator, and
  CalculationInterpolation types to represent types of arguments that may
  exist as part of a calculation.

• Add a new Value.assertCalculation() method.

• Add a new Number.hasCompatibleUnits() method.

v1.39.2

Compare Source

• Fix a bug where configuring with @use ... with would throw an error when
  that variable was defined in a module that also contained @forward ... with.

v1.39.1

Compare Source

• Partial fix for a bug where @at-root does not work properly in nested
  imports that contain @use rules. If the only @use rules in the nested
  import are for built-in modules, @at-root should now work properly.

v1.39.0

Compare Source

JS API

• Add a charset option that controls whether or not Sass emits a
  @charset/BOM for non-ASCII stylesheets.

v1.38.2

Compare Source

• No user-visible changes

v1.38.1

Compare Source

• No user-visible changes

v1.38.0

Compare Source

• In expanded mode, emit characters in Unicode private-use areas as escape
  sequences rather than literal characters.

• Fix a bug where quotes would be omitted for an attribute selector whose value
  was a single backslash.

• Properly consider numbers that begin with . as "plain CSS" for the purposes
  of parsing plain-CSS min() and max() functions.

• Allow if to be used as an unquoted string.

• Properly parse backslash escapes within url() expressions.

• Fix a couple bugs where @extends could be marked as unsatisfied when
  multiple identical @extends extended selectors across @use rules.

Command Line Interface

• Strip CRLF newlines from snippets of the original stylesheet that are included
  in the output when an error occurs.

JS API

• Don't crash when a Windows path is returned by a custom Node importer at the
  same time as file contents.

• Don't crash when an error occurs in a stylesheet loaded via a custom importer
  with a custom URL scheme.

Dart API

• Add a SassArgumentList.keywordsWithoutMarking getter to access the keyword
  arguments of an argument list without marking them accessed.

svg/svgo

v2.8.0

Compare Source

If you enjoy SVGO and would like to support our work, consider sponsoring us directly via our OpenCollective.

Join us in our discord

Features and bug fixes

• added --no-color flag for testing purposes but you may find it useful (https://github.com/svg/svgo/pull/1588)
• handle url() in style attributes properly (https://github.com/svg/svgo/pull/1592)
• removeXMLNS plugin now removes xmlns:xlink attribute (https://github.com/svg/svgo/pull/1508)
• load .cjs configuration only with require to fix segfaults in linux (https://github.com/svg/svgo/pull/1605)

Refactorings

• simplified and covered with types svg stringifier (https://github.com/svg/svgo/pull/1593)
• migrated to visitor api and covered with types removeEmptyAttrs plugin (https://github.com/svg/svgo/pull/1594)
• migrated to visitor api and covered with types inlineStyles plugin (https://github.com/svg/svgo/pull/1601)
• migrated to picocolors (https://github.com/svg/svgo/pull/1606)

DX

I found some users are trying to enable plugins which are not part of default preset, for example

{
  name: 'preset-default',
  params: {
    overrides: {
      cleanupListOfValues: true
    }
  }
}

To fix this I made docs more concrete about plugin (svg/svgo@5165ccb)
and introduced a warning when true is specified in overrides (svg/svgo@cb7e9be).
Please give us feedback if you still have issues.

Thanks to @​IlyaSkriblovsky, @​devongovett, @​matheus1lva, @​omgovich, @​renatorib and @​TrySound

---

Configuration

📅 Schedule: "before 3am on the first day of the month" (UTC).

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

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[webteam-app]

renovate[bot] is not a collaborator of the repo