Skip to content

Commit d45e8dd

Browse files
docs: nicer quotes
It's generally a good practice to prefer single-quotes in shell script strings unless you plan on interpolating environment variables. It's purely stylistic here, but there's something about shell code that looks safer at first-glance. It's sorta like the how SQL query string _can_ be safe when concatenating another string directly onto it, but it doesn't _look_ as safe at first glance as one that escapes the inputs. Plus, given that the NPM script is already inside a JSON string, getting rid of the escaped characters makes it look neater! :3
1 parent 11500d4 commit d45e8dd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Otherwise **concurrently** would try to run 4 separate commands:
7070
In package.json, escape quotes:
7171

7272
```bash
73-
"start": "concurrently \"command1 arg\" \"command2 arg\""
73+
"start": "concurrently 'command1 arg' 'command2 arg'"
7474
```
7575

7676
You can always check concurrently's flag list by running `concurrently --help`.

0 commit comments

Comments
 (0)