Skip to content

Commit 84292a2

Browse files
authored
Move note upper
Move note upper
1 parent 236da25 commit 84292a2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,7 @@ Possible workarounds include:
113113
> **The Key Change:** On Windows, running a Node.js package via `npx` often requires the `cmd /c` prefix to be executed correctly from within another process like VSCode's extension host. Therefore, `"command": "npx"` was replaced with `"command": "cmd"`, and the actual `npx` command was moved into the `"args"` array, preceded by `"/c"`. This fix allows Windows to interpret the command correctly and launch the server.
114114
115115
- **Solution 2** Instead of another layer of shell you can write the absolute path to `npx`:
116+
> Note: The path below is an example. You must adjust it to match the actual location of `npx` on your machine. Depending on your setup, the file extension might be `.cmd`, `.bat`, or `.exe` rather than `.ps1`. Also, ensure you use double backslashes (`\\`) as path delimiters, as required by the JSON format.
116117
```json
117118
"mcpServers": {
118119
"chrome-devtools": {
@@ -121,4 +122,3 @@ Possible workarounds include:
121122
}
122123
}
123124
```
124-
Note: The path above is an example. You must adjust it to match the actual location of `npx` on your machine. Depending on your setup, the file extension might be `.cmd`, `.bat`, or `.exe` rather than `.ps1`. Also, ensure you use double backslashes (`\\`) as path delimiters, as required by the JSON format.

0 commit comments

Comments
 (0)