You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 6, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -137,6 +137,13 @@ contains special shell characters *that you want interpreted*, then use
137
137
138
138
On Windows you need to use `cross-env-shell`, if you want to handle [signal events](https://nodejs.org/api/process.html#process_signal_events) inside of your program. A common case for that is when you want to capture a `SIGINT` event invoked by pressing `Ctrl + C` on the command-line interface.
139
139
140
+
## Windows Issues
141
+
142
+
Please note that `npm` uses `cmd` by default and that doesn't support command
143
+
substitution, so if you want to leaverage that, then you need to update your
144
+
`.npmrc` to set the `script-shell` to powershell.
145
+
[Learn more here](https://github.com/kentcdodds/cross-env/issues/192#issuecomment-513341729).
146
+
140
147
## Inspiration
141
148
142
149
I originally created this to solve a problem I was having with my npm scripts in
0 commit comments