Skip to content

Remove unused or duplicate frontend dependencies #1625

Closed
#1692
Closed
Remove unused or duplicate frontend dependencies#1625
#1692
Assignees
walexjnr
Labels
Stellar WaveIssues in the Stellar wave programenhancementNew feature or requestfrontend

Description

@yusuftomilola
yusuftomilola
opened on Oct 16, 2026

Problem

jspdf and qrcode are declared but never imported in app/, components/, features/, lib/ or hooks/; @types/recharts is obsolete because recharts 3 ships its own types and can conflict with them; react-toastify is imported in a single file while the app also has its own components/ui/toast.tsx, so there are two toast systems.

Proposed change

Remove what is unused, pick one toast implementation, and re-run lint, type-check and build to confirm nothing broke. If PDF/QR features are planned, link the issue that will use them.

Acceptance criteria

  • depcheck reports no unused dependencies; bundle size does not grow.

Activity

  1. yusuftomilola
    added
    enhancementNew feature or request
    frontend
    on Oct 16, 2026
  2. drips-wave
    added
    Stellar WaveIssues in the Stellar wave program
    on Oct 17, 2026

  3. Micheal1605 commented on Oct 17, 2026

    @Micheal1605
    Micheal1605
    on Oct 17, 2026 – with Drips Wave

    @Micheal1605 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi Maintainer,
    I'd like to work on this issue. I've reviewed the problem and understand that the project contains potentially unused dependencies, an obsolete Recharts type package, and two competing toast notification systems.
    Here's what I'd do:
    Audit the project's dependencies and remove jspdf and qrcode if they're genuinely unused, checking for indirect references and planned integrations before removing them.
    Remove @types/recharts, since Recharts 3 provides its own TypeScript definitions.
    Standardise toast notifications on the existing components/ui/toast.tsx implementation, replacing the react-toastify usage while preserving the current notification behaviour and styling.
    Update the relevant dependency manifests and lockfile to keep the dependency tree consistent.
    Run depcheck, lint, TypeScript checks, and the production build to verify that the changes introduce no regressions. I'll also compare bundle sizes to confirm they don't grow.
    I'll keep the changes focused on dependency cleanup, preserve existing functionality, and document any PDF or QR functionality that requires a separate implementation issue.
    Please consider assigning this issue to me. Thank you!

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Micheal1605 to this issue.

  4. walexjnr commented on Oct 17, 2026

    @walexjnr
    walexjnr
    on Oct 17, 2026 – with Drips Wave
    Contributor

    @walexjnr has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi, am a full stack developer. I will like to work on this

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @walexjnr to this issue.

  5. yusuftomilola
    assigned
    walexjnr
    on Oct 17, 2026

  6. drips-wave commented on Oct 17, 2026

    @drips-wave
    drips-waveBot
    on Oct 17, 2026 – with Drips Wave

    Congratulations, @walexjnr! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @walexjnr: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  7. yusuftomilola
    closed this as completedin #1692on Oct 17, 2026

  8. grantfox-oss commented on Oct 17, 2026

    @grantfox-oss
    grantfox-ossBot
    on Oct 17, 2026 – with GrantFox OSS

    🎉 This issue has been marked as completed on GrantFox!

    @walexjnr's PR #1692 was approved and merged by @yusuftomilola.

    🏆 @walexjnr: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,348 total points). Track your full progress on GrantFox.

    👏 Great work, @walexjnr! Keep contributing to DistinctCodes.

  9. drips-wave commented on Oct 17, 2026

    @drips-wave
    drips-waveBot
    on Oct 17, 2026 – with Drips Wave

    This issue has been completed by @walexjnr as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @walexjnr: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

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

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programenhancementNew feature or requestfrontend

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions