fix: Update the payments page

[jhechtf]

TL;DR

Updated SvelteKit and Svelte to latest versions, added new Card component with stories, implemented payment grouping by household, and created experimental form attachment utilities.

What changed?

• Framework Updates: Upgraded @sveltejs/kit from v2.47.0 to v2.53.4 and svelte from v5.36.5 to v5.53.6
• New Components: Added a flexible Card component with header, footer, and content slots, including comprehensive Storybook stories
• Payment Enhancements:
  • Added getCurrentPaymentsByHousehold() function to group payments by household
  • Updated payment queries to filter by current year in addition to current month
  • Modified payments page to display payments grouped by household name
• Experimental Features: Created useRemote attachment utility for enhanced form handling with documentation
• Developer Experience:
  • Added TUI mode to turbo dev command
  • Enhanced error boundary to show error messages in development
  • Removed debug console.log statements
• Bug Fixes: Added missing amount field to bulk bill editing functionality

How to test?

1. Verify the payments page now groups payments by household
2. Test the new Card component in Storybook with different configurations (default, summary, with image)
3. Ensure bill editing includes the amount field
4. Check that payment filtering correctly shows only current year/month payments

Why make this change?

The framework updates provide latest features and bug fixes. The payment grouping improves UX by organizing payments more logically. The Card component provides a reusable UI building block. The experimental form utilities explore better form handling patterns for future implementation.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bill-tracker-mono	Ready	Preview, Comment	Mar 4, 2026 6:39am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 303b7f30-b8a1-4eb2-870a-a73d39275f97

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch can-we-fix-the-payments-page

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jhechtf]

• fix: Update the payments page #134 👈 (View in Graphite)
• feat: begin move to remote functions #133 : 4 other dependent PRs (#135 , #136 , #137 and 1 other)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.