Skip to content
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

Use npm config object over custom. #297

Closed
joshmanders opened this issue Oct 19, 2015 · 1 comment

Comments

@joshmanders
Copy link

commented Oct 19, 2015

Is there any specific reason that standard exists on the root package.json object and not in the global config object? https://docs.npmjs.com/files/package.json#config

@feross

This comment has been minimized.

Copy link
Member

commented Oct 19, 2015

Interesting. Didn't know about the "config" property when we added the "standard" option. There's already a popular practice of just adding config options directly to the root of package.json, for example: "browserify" and "browser" are two that I'm aware of.

@feross feross closed this Oct 19, 2015

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.