Skip to content
This repository has been archived by the owner on May 17, 2022. It is now read-only.

Update dependency postcss to v8.4.13 #169

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 24, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
postcss (source) 8.3.11 -> 8.4.13 age adoption passing confidence

Release Notes

postcss/postcss

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 append() error after using .parent (by Jordan Pittman).

v8.4.0

Compare Source

President Camio seal

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.

Sponsored by Tailwind CSS Sponsored by ThemeIsle

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:

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.

PostCSS install size reduction #### 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


Configuration

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

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

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot changed the title Update dependency postcss to v8.4.0 Update dependency postcss to v8.4.1 Nov 24, 2021
@renovate renovate bot force-pushed the renovate/postcss-8.x branch 2 times, most recently from 1173ad1 to 02619a5 Compare November 26, 2021 19:51
@renovate renovate bot changed the title Update dependency postcss to v8.4.1 Update dependency postcss to v8.4.3 Nov 26, 2021
@renovate renovate bot force-pushed the renovate/postcss-8.x branch from 02619a5 to 30fe256 Compare November 27, 2021 15:50
@renovate renovate bot changed the title Update dependency postcss to v8.4.3 Update dependency postcss to v8.4.4 Nov 27, 2021
@renovate renovate bot force-pushed the renovate/postcss-8.x branch 4 times, most recently from a47e30b to 6c7ca59 Compare December 6, 2021 21:55
@renovate renovate bot force-pushed the renovate/postcss-8.x branch 4 times, most recently from f6d31d4 to 83db4c5 Compare December 13, 2021 00:57
@renovate renovate bot changed the title Update dependency postcss to v8.4.4 Update dependency postcss to v8.4.5 Dec 13, 2021
@renovate renovate bot force-pushed the renovate/postcss-8.x branch from 83db4c5 to 63e2da4 Compare February 1, 2022 12:51
@renovate renovate bot changed the title Update dependency postcss to v8.4.5 Update dependency postcss to v8.4.6 Feb 1, 2022
@renovate renovate bot force-pushed the renovate/postcss-8.x branch from 63e2da4 to 2727f3c Compare March 7, 2022 07:58
@renovate renovate bot changed the title Update dependency postcss to v8.4.6 Update dependency postcss to v8.4.8 Mar 7, 2022
@renovate renovate bot changed the title Update dependency postcss to v8.4.8 Update dependency postcss to v8.4.12 Mar 26, 2022
@renovate renovate bot force-pushed the renovate/postcss-8.x branch from 2727f3c to 84889e7 Compare March 26, 2022 15:40
@renovate renovate bot changed the title Update dependency postcss to v8.4.12 Update dependency postcss to v8.4.13 May 15, 2022
@renovate renovate bot force-pushed the renovate/postcss-8.x branch from 84889e7 to aab2156 Compare May 15, 2022 22:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant