fix: replace Axios responseType stream with native fetch for browser compatibility - #19
Merged
Merged
Conversation
Senthil455
commented
Jun 17, 2026
Senthil455
left a comment
Owner
Author
There was a problem hiding this comment.
gh: Not Found (HTTP 404)
{"message":"Not Found","documentation_url":"https://docs.github.com/rest/issues/comments#get-an-issue-comment","status":"404"}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
copilotApi.chat.stream() used api.post(..., { responseType: "stream" }) which is an Axios feature only available in Node.js. In browser environments, Axios does not support responseType: "stream" — the call would silently fail or throw.
Solution
Replaced the Axios call with native fetch() that returns a Promise. The response body provides a ReadableStream via response.body.getReader() which is the standard browser API for consuming streaming responses.
The Authorization header is set from the in-memory token (via getAccessToken()), consistent with the rest of the API layer.