-
Notifications
You must be signed in to change notification settings - Fork 49
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
support init-type
config
#654
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
With the current trends of node developers tending to write es6 modules instead of commonjs ones, there is immediate value to be had by allowing users to set a default type for new modules when running
npm init
Describe the solution you'd like
The
init-type
(orinit.type
) field should be supported. The default should be set tocommonjs
and the only other allowed valuemodule
.Describe alternatives you've considered
Users could write their own init module, but documentation there is lacking and this field impacts all of the nodejs community in some way. It's best to support it as a first class value.
Additional context
npm/rfcs#347
The text was updated successfully, but these errors were encountered: