Skip to content

fix: pin Kapwa 1.2.4 and harden home section for forks - #78

Open
kuyacarlo wants to merge 1 commit into
BetterLosBanos:mainfrom
kuyacarlo:feat/pin-kapwa-and-gov-badges
Open

fix: pin Kapwa 1.2.4 and harden home section for forks#78
kuyacarlo wants to merge 1 commit into
BetterLosBanos:mainfrom
kuyacarlo:feat/pin-kapwa-and-gov-badges

Conversation

@kuyacarlo

@kuyacarlo kuyacarlo commented Aug 3, 2026

Copy link
Copy Markdown

Summary

  • Exact-pin @bettergov/kapwa@1.2.4 and Tailwind 4.2.0 so floating ^ ranges cannot pull Kapwa 1.4.x (which moves semantic colors out of @theme and drops text-kapwa-text-inverse / related utilities).
  • Derive government badge counts from barangays.json / departments.json instead of hardcoded Los Baños numbers.
  • Gate hero Quick Access “Legislation” on features.openLGU; fall back to Government when OpenLGU is off.
  • Soften weather offline/503 copy and drop the losBanos variable name.

Found while forking BetterBulakan: a clean pnpm install of ^1.2.4 resolved to Kapwa 1.4.1 and broke hero/ticker contrast on blue/navy backgrounds.

Test plan

  • npm install then npm run build — CSS contains .text-kapwa-text-inverse
  • Home hero title is white on blue
  • Government badges match directory JSON lengths
  • With features.openLGU: false, Quick Access shows Government instead of /openlgu
  • With weather API down, UI shows friendly offline message

Made with Cursor

Exact-pin Kapwa and Tailwind so forks using floating ranges cannot pull
Kapwa 1.4.x and silently drop semantic text utilities. Derive barangay
and department badge counts from directory JSON, gate hero Legislation
on features.openLGU, and soften offline weather copy.

Co-authored-by: Cursor <cursoragent@cursor.com>

@miconficker miconficker left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Looks good to me! Thank you for your contribution to make this better for forks. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants