-
Notifications
You must be signed in to change notification settings - Fork 53
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
make the license field of npm init
more stubborn
#655
Comments
This is great - we should definitely include a link to help users choose. |
Is there any update on this? Having |
@aretrace you can set an npm config for init.license and address that problem. |
@ljharb I did not know that, thanks! I would still advocate for an interactive confirmation user prompt. |
Is your feature request related to a problem? Please describe.
Currently we set licenses to
ISC
by defaultDescribe the solution you'd like
We should not select a default license on behalf of our users. Instead we should default to omitting the license field entirely in non-interactive mode, and in interactive mode require that the user either provides a value or confirms that they do not want to select a license at all. As a bonus it would be nice if we had a site to link to that helps our users select a license that fits their needs.
Describe alternatives you've considered
The license default could change, but a new default means that we are once again providing a default that may not align with users needs. It feels best to not provide a license by default at all.
Additional context
npm/rfcs#597
The text was updated successfully, but these errors were encountered: