Update dependency postcss to v8.4.16

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
postcss (source)	8.3.6 -> 8.4.16

---

Release Notes

postcss/postcss

v8.4.16

Compare Source

• Fixed Root AST migration.

v8.4.15

Compare Source

• Fixed AST normalization after using custom parser with old PostCSS AST.

v8.4.14

Compare Source

• Print “old plugin API” warning only if plugin was used (by @​zardoy).

v8.4.13

Compare Source

• Fixed append() error after using .parent (by Jordan Pittman).

v8.4.12

Compare Source

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

v8.4.11

Compare Source

• Fixed Declaration#raws.value type.

v8.4.10

Compare Source

• Fixed package.funding URL format.

v8.4.9

Compare Source

• Fixed package.funding (by Álvaro Mondéjar).

v8.4.8

Compare Source

• Fixed end position in empty Custom Properties.

v8.4.7

Compare Source

• Fixed Node#warn() type (by Masafumi Koba).
• Fixed comment removal in values after ,.

v8.4.6

Compare Source

• Prevented comment removing when it change meaning of CSS.
• Fixed parsing space in last semicolon-less CSS Custom Properties.
• Fixed comment cleaning in CSS Custom Properties with space.
• Fixed throwing an error on .root access for plugin-less case.

v8.4.5

Compare Source

• Fixed raws types to make object extendable (by James Garbutt).
• Moved from Yarn 1 to pnpm.

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 Root AST migration.

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).

v8.3.11

Compare Source

• Remove debugging code.

v8.3.10

Compare Source

• Fixed Maximum call stack issue of some source maps (by Yeting Li).

v8.3.9

Compare Source

• Replaced nanocolors to picocolors.
• Reduced package size.

v8.3.8

Compare Source

• Update nanocolors.

v8.3.7

Compare Source

• Replaced colorette to nanocolors.
• Added bug field to package.json (by Christian Oliff).
• Improved docs (by Andrew Bruce and Paul Shryock).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 Mend Renovate. View repository job log here.