chore: move pnpm overrides to pnpm-workspace.yaml

Open Beginner friendly
#8,601 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Domain
build-system, tooling

Research direction

Inspect the dashboard package.json and pnpm-workspace.yaml to compare the current overrides with pnpm 10's workspace configuration. Run the dashboard install and lockfile refresh, then verify the warning is gone, both dependency pins remain effective, the lockfile is consistent, and any install documentation still matches.

Written by the indexing model from the issue text.

Description

area:webui

What to build

Move dashboard dependency overrides out of package.json's deprecated pnpm.overrides field into the pnpm 10-supported workspace configuration so dependency pins continue to apply during installs and lockfile refreshes.

Acceptance criteria

  • pnpm no longer prints the warning that package.json pnpm.overrides is ignored.
  • The immutable and lodash-es overrides remain effective after install.
  • The lockfile remains consistent after the override location change.
  • CI/dashboard install documentation, if any, still matches the workspace setup.

Blocked by

None - can start immediately

Dominant language
Python
Stars
40.7k
Forks
2.9k
Avg merge
1d 5h
Merged PRs (30d)
112

Contributor guide

Open the contributing guide

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 AstrBotDevs/AstrBot

All issues in AstrBotDevs/AstrBot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.