Adopt @spudly/ui 3.0.0: page-only consumption + loading prop rename

Open
  • Is something wrong?
#413 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react, typescript
Domain
frontend

Research direction

Start by inventorying current master for @spudly/ui imports and isLoading call sites, then review the design-system changelog for the 2.x to 3.0.0 changes. Prepare an implementation plan for Stephen's approval before making changes; after approval, update the dependency and migrate the imports and props. Done means the app uses page-only exports, all affected props use loading, and manual checks cover the changelog delta.

Written by the indexing model from the issue text.

Description

blocked in_progress priority-p2

Adopt @spudly/ui 3.0.0 (published 2026-11-03 via design-system PR #390)

Version 3.0.0 is a double major for consumers:

  • #298 — pages-only exports: the package root now exports page components only. Every root import of a widget/icon/form composite (Button, Card, Text, etc.) breaks. Eciperay must consume pages exclusively; anything the app composes from widgets today has to be re-expressed through the page components (or surfaced as a DS gap — file in design-system, don't work around locally).
  • #278 — isLoading prop renamed to loading everywhere. Eciperay has ~19 call sites to rename.

Scope

  1. Bump @spudly/ui to 3.0.0 (minimal-delta lockfile discipline applies — preserve the Tamagui 3.0.15 nested layout; never hand-resolve the lockfile).
  2. Migrate every non-page import to page-only consumption; rename isLoading → loading at all call sites.
  3. Manual test scope comes from the DS changelog delta for the 2.x → 3.0.0 range (the repo-manager MANUAL PR TEST rule), not from the app diff.

Plan gate applies: an implementation plan goes on this issue as a comment for Stephen's approval before implementation — the plan should inventory the actual widget imports and call sites found on current master, since the counts above date from 2026-11-03.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
8h 56m
Merged PRs (30d)
200

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spudly/eciperay

All issues in spudly/eciperay

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.