chore(deps): remove primeflex - #2317
Open
isaque-bock-azion wants to merge 1 commit into
Open
Conversation
The package was only used for 13 utility classes (surface-hover, surface-border, surface-section, surface-card, surface-ground, surface-0/50/ 200/400, text-color, text-color-secondary), all thin wrappers around azion-theme's own --surface-*/--text-color* CSS variables -- primeflex's thousands of other flex/grid/spacing utilities were unused. Recreate just that subset as Tailwind v4 @Utility rules in main.css, following the same pattern already used there for px-shell/px-container. `@import 'tailwindcss' important` already applies !important to every generated utility, matching primeflex's own !important-by-default classes, so no extra flag is needed.
isaque-bock-azion
force-pushed
the
chore/remove-primeflex
branch
from
August 19, 2026 20:06
5dfbcc2 to
6b81546
Compare
isaque-bock-azion
marked this pull request as ready for review
August 19, 2026 22:44
isaque-bock-azion
requested review from
a team,
bruno-andrade-azion,
marcus-souza-azion and
pedro-ribeiro-azion
as code owners
August 19, 2026 22:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fourth PR in the docs modernization stack (base: #2316). Removes the
primeflexdependency.Why it's safe
The package was only ever used for 13 utility classes across 31 files:
surface-hover,surface-border,surface-section,surface-card,surface-ground,surface-0/50/200/400,text-color,text-color-secondary. Every one of them is a thin wrapper around anazion-themeCSS variable (.text-color { color: var(--text-color) }) — the values come fromazion-theme, not from primeflex itself, andazion-themestays installed regardless of this PR.What changed
@utilityrules in main.css, matching the pattern already used there forpx-shell/px-container. The project's global@import 'tailwindcss' importantalready forces!importanton every generated utility, matching primeflex's own!important-by-default classes — no extra flag needed.primeflex/primeflex.cssimport fromBaseLayout.astroand theprimeflexentry frompackage.json.Verification
pnpm run build:local: 1494 pages, no errors. Confirmed the compiled CSS carries the expected rules (e.g..surface-hover{background-color:var(--surface-hover)!important}).astro preview(production build): header (surface-ground/surface-border, 24 elements using these classes on a single doc page), search dialog (surface-sectionpanel background, real Algolia results), left sidebar (current-page item highlighted viasurface-200) — all render identically to before, zero console errors.🤖 Generated with Claude Code