Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Aug 11, 2022. It is now read-only.

Conversation

lennym
Copy link
Contributor

@lennym lennym commented Jun 20, 2017

If a user mistakenly shorthands npm build for npm run build then they currently get no output or information since npm build without arguments is a no-op.

If npm build is called without arguments when a build script is defined in the package.json scripts section then output a warning message to indicate this.

See #3927

If a user mistakenly shorthands `npm build` for `npm run build` then they currently get no output or information since `npm build` without arguments is a no-op.

If `npm build` is called without arguments when a `build` script is defined in the package.json `scripts` section then output a warning message to indicate this.

See npm#3927
@iarna
Copy link
Contributor

iarna commented Jun 27, 2017

Thanks! This would definitely save folks a lotta trouble. It's been merged as 82df7bb.

@iarna iarna closed this Jun 27, 2017
iarna pushed a commit that referenced this pull request Jun 27, 2017
If a user mistakenly shorthands `npm build` for `npm run build` then they currently get no output or information since `npm build` without arguments is a no-op.

If `npm build` is called without arguments when a `build` script is defined in the package.json `scripts` section then output a warning message to indicate this.

Fixes: #3927
PR-URL: #17351
Credit: @lennym
Reviewed-By: @iarna
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants