@inquirer/prompts 7.8.2 → 7.8.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +5 -0
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -181,6 +181,11 @@ The context options are:
181
181
  | clearPromptOnDone | `boolean` | no | If true, we'll clear the screen after the prompt is answered |
182
182
  | signal | `AbortSignal` | no | An AbortSignal to cancel prompts asynchronously |
183
183
 
184
+ > [!WARNING]
185
+ > When providing an input stream or piping `process.stdin`, it's very likely you need to call `process.stdin.setRawMode(true)`
186
+ > before calling inquirer functions. Node.js usually does it automatically, but when we shadow the stdin, Node can loss track
187
+ > and not know it has to. If the prompt isn't interactive (arrows don't work, etc), it's likely due to this.
188
+
184
189
  Example:
185
190
 
186
191
  ```js
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@inquirer/prompts",
3
- "version": "7.8.2",
3
+ "version": "7.8.3",
4
4
  "description": "Inquirer prompts, combined in a single package",
5
5
  "keywords": [
6
6
  "answer",
@@ -77,7 +77,7 @@
77
77
  },
78
78
  "dependencies": {
79
79
  "@inquirer/checkbox": "^4.2.1",
80
- "@inquirer/confirm": "^5.1.14",
80
+ "@inquirer/confirm": "^5.1.15",
81
81
  "@inquirer/editor": "^4.2.17",
82
82
  "@inquirer/expand": "^4.0.17",
83
83
  "@inquirer/input": "^4.2.1",
@@ -112,5 +112,5 @@
112
112
  "optional": true
113
113
  }
114
114
  },
115
- "gitHead": "daf4d6f08a55ab0e0cca61d95ec0f579e7b3e698"
115
+ "gitHead": "df341a8094bde7687225143bb0b4cf932846be4f"
116
116
  }