Skip to content

[Repo] Remove unused dependencies from the root package.json #1449

Closed

Description

@BigBen-7

Found in a repository audit of main (b472e6b). The facts below were checked against that commit.

Problem

The root package.json exists only for husky (prepare), yet it declares chart.js, chartjs-plugin-annotation and react-chartjs-2 as dependencies and @types/react as a devDependency. The root has no application code (Frontend/ and analytics/ have their own manifests).

Fix

Remove everything except husky and regenerate the root package-lock.json.

Acceptance criteria

  • Root manifest only lists what the root actually needs
  • npm install at the root still installs the git hooks

Notes

Scope: Light (about half a day or less). Location: package.json, package-lock.json.

Activity

  1. guptakumarranjeet150 commented on Oct 14, 2026

    @guptakumarranjeet150

    Hi team,

    I analyzed "[Repo] Remove unused dependencies from the root package.json" in PinSpace-Org/GistPin and have a concrete technical roadmap to resolve it.

    Technical Implementation Outline:

    1. Inspect package manifest (package.json), peer dependency declarations, and module resolution in package.js.
    2. Configure explicit peer/optional dependencies and alignment to prevent missing runtime modules.
    3. Verify package lockfile generation and run isolated installation with zero manual steps.
    4. Validate full package build, typecheck, and runtime initialization succeed without errors.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  2. sage9ty commented on Oct 17, 2026

    @sage9ty

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

    I’ve gone through the issue and have a good idea of how to solve it. Let me work on it.

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

  3. Mentor-drip commented on Oct 17, 2026

    @Mentor-drip

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

    Ready to learn fast and exceed expectations.

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

  4. hauwauyahass-byte commented on Oct 17, 2026

    @hauwauyahass-byte

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

    I'd be glad to handle this issue. I'll keep the implementation concise, maintainable, and well-documented.

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

  5. mxllv commented on Oct 17, 2026

    @mxllv
    Contributor

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

    Hi, I'd like to take this on.

    This touches React, which I have hands-on experience with. I'll refactor this cleanly without changing existing behavior, keeping the diff focused and easy to review.

    Planned approach, based on the acceptance criteria:

    • Root manifest only lists what the root actually needs
    • npm install at the root still installs the git hooks

    I'd appreciate being assigned to this issue and look forward to contributing.

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

  6. drips-wave commented on Oct 17, 2026

    @drips-wave

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

    🧑‍💻 @mxllv: 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. grantfox-oss commented on Oct 17, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @mxllv's PR #1530 was approved and merged by @BigBen-7.

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

    👏 Great work, @mxllv! Keep contributing to PinSpace-Org.

  8. drips-wave commented on Oct 17, 2026

    @drips-wave

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

    😎 @mxllv: 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 programcleanupDead code / housekeepingdependenciesDependency changes

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions