-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: npm fund depth #152
base: main
Are you sure you want to change the base?
RFC: npm fund depth #152
Conversation
This is my first time submitting an RFC to npm 🎉. 🤞 that I did it correctly. However if I didn't, please let me know and I'll make any corrections needed. I look forward to discussing this RFC and answering any questions that arise with the community! |
|
||
Drawbacks: | ||
|
||
- Funding bloat happens quickly. It's impossible to fund all dependencies, and users are more likely to fund direct dependencies since they know how they interact with them and utilize them directly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens if one of your direct deps has no funding info, but it depends on dozens of packages that do declare funding info?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ljharb In this case, if you set depth=0
I believe it should not output the sub-dependencies funding information. It should be strictly limited to printing funding information of your direct dependencies.
I wish there was an existing example of that behavior that we could emulate, however I can't think of a similar example for this case.
Do you think I should clarify that more in the document?
Co-authored-by: Jordan Harband <ljharb@gmail.com>
hi @fishcharlie, first of all thanks for the contribution 😊 I'm going to leave here the feedback we got from the last time we discussed it (as we went over it again during this week's npm OpenRFC call). In most of npm subcommands, we're shifting the focus away from the There were a bunch of discussions when we first set to remove support to An important change @isaacs noticed is that we'd still want to preserve the default behavior of Next action item here now is to tweak the RFC to reflect these proposed changes 😄 |
Formatted RFC
What / Why
References