mirror of
https://github.com/pnpm/pnpm.git
synced 2026-05-11 17:42:43 -04:00
45 lines
1.6 KiB
Markdown
45 lines
1.6 KiB
Markdown
---
|
|
name: Feature request 🔮
|
|
about: Propose a concrete new feature
|
|
title: ''
|
|
labels: 'type: feature'
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
<!--
|
|
These issues are for **concrete and actionable proposals**. If you just have
|
|
a general problem that you would like to brainstorm, open a Discussion instead (https://github.com/pnpm/pnpm/discussions).
|
|
-->
|
|
|
|
<!--
|
|
If this feature request many people in a company/big team, create a post for your company in the following discussion:
|
|
https://github.com/pnpm/pnpm/discussions/3787
|
|
and link the issue in your post.
|
|
|
|
This will help us prioritize issues that affect more people.
|
|
-->
|
|
|
|
- [ ] I'd be willing to implement this feature ([contributing guide](https://github.com/pnpm/pnpm/blob/main/CONTRIBUTING.md))
|
|
|
|
**Describe the user story**
|
|
|
|
A clear and concise description of what workflow is meant to be improved.
|
|
Example: "As a developer, I often want to do <something>, but I often face <problem>".
|
|
|
|
**Describe the solution you'd like**
|
|
|
|
A clear and concise description of what you want to happen. Consider that pnpm is used
|
|
by many people, and your particular use case might not make sense to implement in the core.
|
|
|
|
**Describe the drawbacks of your solution**
|
|
|
|
This section is important not only to identify future issues, but also for us to see whether
|
|
you thought through your request. When filling it, ask yourself what are the problems we could
|
|
have maintaining what you propose. How often will it break?
|
|
|
|
**Describe alternatives you've considered**
|
|
|
|
A clear and concise description of any alternative solutions or features you've considered,
|
|
and why you think they wouldn't be good enough.
|