fix(deps): update dependency postcss-import to v16

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
postcss-import	^12.0.0 -> ^16.0.0

---

Release Notes

postcss/postcss-import (postcss-import)

v16.1.0

Compare Source

• Allow bundling URLs with fragments (useful for Vite users) (#​560, #​561)

v16.0.1

Compare Source

• Fix crash when handling some @imports with media conditions (#​557, #​558)

v16.0.0

Compare Source

• BREAKING: Require Node.js v18+ (#​550, #​551)
• BREAKING: Signifigant rewrite, with small behavioral tweaks in a number of edge cases
• Support for @supports conditional imports added (#​532, #​548)
• When skipDuplicates is false, handles import cycles correctly (#​462, #​535)
• Add warnOnEmpty option to allow disabling warnings for empty files (#​84, #​541)
• Use proper node.errors (#​518, #​540)

Huge thanks to @romainmenke for all the hard work he put into this release.

v15.1.0

Compare Source

• Add data: URL support (this is not useful for most consumers) (#​515)

v15.0.1

Compare Source

• Preserve layer in ignored @imports (#​510, #​511)
• Join media queries in the correct order (#​512, #​513)

v15.0.0

Compare Source

• BREAKING: Require Node.js v14+ (#​497)
• BREAKING: Require nameLayer option for handling anonymous layers (#​496)
• Fix handling of @media queries inside layered imports (#​495, #​496)

v14.1.0

Compare Source

• Add @layer support (#​483)

v14.0.2

Compare Source

• Remove remaining direct import of postcss package (#​455, #​456)

v14.0.1

Compare Source

• Fix bug with @charset statements in media imports (#​448, #​453)

v14.0.0

Compare Source

This release should not have breaking changes for the vast majority of users; only those with @charset statements in their CSS may be affected.

• BREAKING: Error if multiple incompatible @charset statements (#​447)
• BREAKING: Warn if @charset statements are not at the top of files (#​447)
• Fix handing of @charset (#​436, #​447)

v13.0.0

Compare Source

• BREAKING: Require Node 10+ (#​429)
• BREAKING: Upgrade to postcss v8 and require it as a peerDependency (#​427, #​432)
• Update dependencies

---

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, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/postcss-import
npm error   postcss-import@"^16.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer postcss-import@"^12.0.0" from [email protected]
npm error node_modules/scratch-webpack-configuration
npm error   dev scratch-webpack-configuration@"3.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/postcss-import
npm error   peer postcss-import@"^12.0.0" from [email protected]
npm error   node_modules/scratch-webpack-configuration
npm error     dev scratch-webpack-configuration@"3.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-02-11T13_00_25_012Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-11T13_00_25_012Z-debug-0.log