claude-code - 💡(How to fix) Fix [Feature Request] Add Chinese language voice support [1 participants]

[{"error":"Error: console.error: [bun] Warning: ws.WebSocket 'unexpected-response' event is not implemented in bun\n at K (/$bunfs/root/src/entrypoints/cli.js:527:11586)\n at emitWarning (ws:43:42)\n at #onOrOnce (ws:170:18)\n at yn_ (/$bunfs/root/src/entrypoints/cli.js:3425:4680)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T18:11:32.713Z"},{"error":"AxiosError: Request failed with status code 404\n at tF (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12744)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T18:13:25.839Z"}]

TL;DR

The issue seems to be related to missing implementation of the 'unexpected-response' event in the WebSocket and a 404 status code error, which may require updating the WebSocket implementation or handling the error.

Guidance

• The error message indicates that the 'unexpected-response' event is not implemented in bun, which could be causing the issue. It might be necessary to update the WebSocket implementation to handle this event.
• The 404 status code error suggests that the requested resource is not found. Verify that the URL being requested is correct and the resource exists.
• Check the version of bun being used (2.1.109) to see if there are any known issues or updates that may address these errors.
• Consider adding error handling for the Axios request to handle the 404 status code error and provide a more informative error message.

Example

No code example is provided as the issue does not contain sufficient information about the code being used.

Notes

The issue lacks information about the code being used, making it difficult to provide a more specific solution. The guidance provided is based on the error messages and may not be comprehensive.

Recommendation

Apply workaround: The issue seems to be related to a missing implementation and a 404 error, which may require a workaround to handle the errors until a more permanent solution is found.