npm scripts documentation is incorrect #1567
Comments
BuckyMaler
added a commit
to BuckyMaler/nx
that referenced
this issue
Jul 7, 2019
Before, a single instance of yargs was accumulating options, so commands parsed later would have options from prior commands. That's because all yargs options are global by default. Now, a new instance of yargs is required before each command is parsed, so global options aren't accumulated. fixes nrwl#1567
BuckyMaler
added a commit
to BuckyMaler/nx
that referenced
this issue
Jul 7, 2019
Before, a single instance of yargs was accumulating options, so commands parsed later would have options from prior commands. That's because all yargs options are global by default. Now, a new instance of yargs is required before each command is parsed, so global options aren't accumulated. fixes nrwl#1567
BuckyMaler
added a commit
to BuckyMaler/nx
that referenced
this issue
Jul 8, 2019
Before, a single instance of yargs was accumulating options, so commands parsed later would have options from prior commands. That's because all yargs options are global by default. Now, a new instance of yargs is required before each command is parsed, so global options aren't accumulated. fixes nrwl#1567
BuckyMaler
added a commit
to BuckyMaler/nx
that referenced
this issue
Jul 20, 2019
Before, a single instance of yargs was accumulating options, so commands parsed later would have options from prior commands. That's because all yargs options are global by default. Now, a new instance of yargs is required before each command is parsed, so global options aren't accumulated. fixes nrwl#1567
vsavkin
pushed a commit
to vsavkin/nx
that referenced
this issue
Aug 6, 2019
Before, a single instance of yargs was accumulating options, so commands parsed later would have options from prior commands. That's because all yargs options are global by default. Now, a new instance of yargs is required before each command is parsed, so global options aren't accumulated. fixes nrwl#1567
vsavkin
pushed a commit
that referenced
this issue
Aug 6, 2019
Before, a single instance of yargs was accumulating options, so commands parsed later would have options from prior commands. That's because all yargs options are global by default. Now, a new instance of yargs is required before each command is parsed, so global options aren't accumulated. fixes #1567
|
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected Behavior
The npm scripts documentation should list only available options for each script/command.
Current Behavior
The npm scripts documentation lists options that aren't available for scripts/commands. For example, many of the options listed in the workspace schematic doc aren't and shouldn't be available to that script/command.
The text was updated successfully, but these errors were encountered: