Proposal: publish to npm using scopes
Open
Nobody has claimed this yet.
pinned
Question
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 809
- PR merge metrics
- No merged PRs in 30d
Description
I think it would make sense to start using scopes when we publish things to npm.
sinon=>@sinonjs/sinonnise=>@sinonjs/niselolex=>@sinonjs/lolexsinon-test=>@sinonjs/sinon-test,@sinonjs/test,@sinonjs/testcaseor some other name
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
Review the proposal and its package-name options for sinon, nise, lolex, and sinon-test. Determine the desired scope and final package names before identifying the publishing changes needed; the work is done when the project has an agreed, consistent scoped-publishing plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100