Skip to content

fix(frontend): override postcss-selector-parser to 7.1.6, keep Tailwind 3 - #844

Merged
soustruh merged 1 commit into
mainfrom
fix/frontend-postcss-selector-parser
Oct 12, 2026
Merged

soustruh merged 1 commit into
mainfrom
fix/frontend-postcss-selector-parser

Conversation

@soustruh

Copy link
Copy Markdown
Contributor

What was wrong

What changed

  • web/frontend/package.json: an npm overrides entry postcss-selector-parser: ^7.1.6. Tailwind stays on 3.4.
  • web/frontend/package-lock.json: postcss-selector-parser 7.1.6.
  • The only breaking change in 7.0.0 is that inserting nodes while walking the tree is now safe. The built CSS is byte-identical to the build from main.

Tests

  • Node 20, as in CI: npm ci, npx tsc --noEmit, npm test and npm run build pass in web/frontend.
  • npm ls shows postcss-selector-parser 7.1.6 everywhere, and npm audit no longer lists it.

After this PR is merged, Dependabot closes #830. A move to Tailwind 4 is separate work: the upgrade tool changes 27 files, and every page needs a visual check.

@keboola-pr-reviewer-bot keboola-pr-reviewer-bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: auto_approve (risk 1/5) · profile _default

Dev-only npm override bumping a build-time CSS parser to patch a Dependabot security alert; safe to auto-approve.

@soustruh
soustruh merged commit 1fefe10 into main Oct 12, 2026
6 checks passed
@soustruh
soustruh deleted the fix/frontend-postcss-selector-parser branch October 12, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants