parse-community / parse-community/parse-server-s3-adapter
Parse should be included as a peerDependency to avoid configuration conflicts in implementing projects
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
Parse is already bundled with parse-server. Since this is an extension for parse-server, it should not include parse itself, but instead expect it as a peerDependencies item. This is important to avoid situations where configuration for parse can get lost due to multiple included libraries including parse in their dependencies list.
Contributor guide
No contributing guide indexed for this repository
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
Inspect the package dependency metadata and compare how parse-server and Parse are currently declared. The work is complete when Parse is no longer a regular dependency and is declared as a peer dependency, with installation and configuration behavior checked for conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100