digidem / digidem/comapeo-core
maybe set mapeo/schema as a peerDepenency
Open
Nobody has claimed this yet.
post-mvp
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 6
- Avg merge
- 1d 40m
- Merged PRs (30d)
- 8
Description
this way all dependencies of mapeo/core (like default-settings, config-builder, mock-data) have all the same version
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 by examining the dependency declarations for mapeo/core and the related packages named in the issue: default-settings, config-builder, and mock-data. Verify how mapeo/schema is currently specified and consider how the dependency versions are aligned. Done means those packages use the same mapeo/schema version through the requested peer dependency arrangement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100