`package.json` spring cleaning
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
In https://github.com/openedx/paragon/issues/3329#issuecomment-3358096022 I mentioned
The other question here is: "should we have
semantic-releasein ourpackage.jsonat all?" Our release workflow usesnpx semantic-release@22, so maybe should just removesemantic-releasefrom thepackage.jsonentirely.
This makes me think it's probably worth looking through our package.json and making sure we actually need the packages we have as dependencies.
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
Start with package.json and compare its dependencies with their use across the repository. Read .github/workflows/release.yml around the npx semantic-release@22 command and the discussion in issue 3329; done means the dependency list reflects packages the project actually needs and the release workflow remains accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100