Fixed version in example package.json
Open
Nobody has claimed this yet.
docs
ready to take
scope: all components
type: new feature
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
It would be easier to know what versions are being packaged in the working example if we had them fixed in the package.json. Is there something that prevents this?
https://github.com/mui-org/material-ui/blob/master/examples/nextjs/package.json
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
Open examples/nextjs/package.json and inspect how its dependency versions are currently specified. Determine which packaged versions should be fixed, then update that file so the example clearly records them; confirm the resulting package manifest remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nextjs
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100