Commit 5bef9f4
fix: propagate mermaid-cli stderr in rendering errors (#83)
* fix: propagate mermaid-cli stderr in rendering errors
When mermaid-cli fails, execFileAsync throws with `.stderr` containing
the actual parse error details (e.g., "Parse error on line 3..."), but
only the generic `error.message` ("Command failed: npx ...") was
surfaced to the MCP response. This made it impossible for Claude to
self-correct Mermaid syntax errors.
Extract stderr from the caught error and include it in the thrown Error
message so that detailed diagnostics reach the MCP client.
* fix: improve catch handler, add tests, fix formatting
---------
Co-authored-by: Vitalii Elenhaupt <velenhaupt@gmail.com>1 parent 0971454 commit 5bef9f4
2 files changed
+54
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
74 | 74 | | |
75 | 75 | | |
76 | 76 | | |
77 | | - | |
78 | | - | |
79 | | - | |
80 | | - | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
81 | 84 | | |
82 | 85 | | |
83 | 86 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| 6 | + | |
6 | 7 | | |
7 | 8 | | |
8 | 9 | | |
| |||
172 | 173 | | |
173 | 174 | | |
174 | 175 | | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
175 | 222 | | |
176 | 223 | | |
177 | 224 | | |
| |||
0 commit comments