neume-network / neume-network/core
For all downstream repositories of core, @neume-network/schema should be a peerDependency
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
- We're again in npm version hell as @neume-network/schema is now being used everywhere individually
- https://github.com/neume-network/core/blob/1cd0595ee009dc109c00855966407561686193cc/package.json#L39
- https://github.com/neume-network/strategies/blob/54631d99cbb1861c9c1381a7b0d5209da7465518/package.json#L50
- https://github.com/neume-network/extraction-worker/blob/ed02ece7d6487363cc8c3db0207ffd979574f66c/package.json#L62
- We once had the same problem with eth-fun until we just said that we make it a mandatory peer dependency in all downstream packages (strategies, extraction worker) and that we truly require it for @neume-network/core though
- This has worked well IMO and so we should do the same now with @neume-network/schema
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 reviewing the package.json dependency entries linked for core, strategies, and extraction-worker, then inspect how the prior eth-fun peer dependency change was handled. Done means schema is treated as a required peer dependency in the downstream packages while core still requires it directly; check each affected package manifest for consistent declarations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100