[RRFC] `workspace-tag-version-prefix` config
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 777
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
Motivation ("The Why")
See https://github.com/npm/cli/issues/4017#issuecomment-1101481619 - npm version should be able to work inside workspaces.
Example
See the OP in https://github.com/npm/cli/issues/4017.
I think adding an npm config of workspace-tag-version-prefix, which defaults to [$workspaceName] - which would result in a tag of [foo] v1.2.3, for example - should address the need.
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 reading the linked npm/cli issue and its referenced original post to understand the workspace versioning requirement. Done means an RFC that clearly specifies the new config's default and resulting workspace tag format, including the [foo] v1.2.3 example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100