Skip to content

Commit 8d3f976

Browse files
authored
docs: fix inconsistencies in passthrough args page
1 parent e3a76f7 commit 8d3f976

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Diff for: docs/cli/passthrough-arguments.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ For example, imagine you have in your `package.json` file scripts like this:
1717
```
1818

1919
If you wanted to run only either `build:server` or `build:client` with an additional `--noEmit` flag,
20-
you can do so with `npm run build:server -- --watch`, for example.<br/>
21-
However, if you want to do that while using concurrently, as `npm run dev -- --noEmit` for example,
22-
you might find that concurrently actually parses `--watch` as its own flag, which does nothing,
20+
you can do so with `npm run build:server -- --noEmit`, for example.<br/>
21+
However, if you want to do that while using concurrently, as `npm run build -- --noEmit` for example,
22+
you might find that concurrently actually parses `--noEmit` as its own flag, which does nothing,
2323
because it doesn't exist.
2424

2525
To solve this, you can set the `--passthrough-arguments`/`-P` flag, which instructs concurrently to

0 commit comments

Comments
 (0)