openedx / openedx/frontend-platform
Remove peer dependency on frontend-build
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 91
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
So in #474, I added a peer dependency on frontend-build because that version of frontend-platform required a sufficiently high version of frontend-build or it would break if added to an MFE.
Now that we're significantly past that version and no MFEs could conceivably need it anymore (v8 of frontend-build), in my opinion we should remove the peer dependency to simplify our dependency graph, rather than continually bumping the dependency higher, which is actually incorrect and just increases our maintenance burden.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the package dependency declaration for frontend-build and inspect how the peer dependency is configured. Remove that peer dependency and verify the package metadata and dependency graph no longer include it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100