MitocGroup / MitocGroup/deepify
Write docs on how deep related packages can be tested locally
Open
Nobody has claimed this yet.
not in scope
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Write docs on how deepify, deep-package-manager and deep-framework can be tested locally without being published to npm to avoid publishing untested code and potential issues.
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 how deepify, deep-package-manager, and deep-framework currently reference one another and how their packages are tested locally. Document a repeatable local-testing workflow that avoids publishing to npm, with completion marked by clear instructions for testing unpublished packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100