You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Personally I don't think the library should expose Axios at all, since it's an internal implementation detail.
For example, in another issue someone asked about how to take advantage of streaming responses from OpenAI. Best I can tell, Axios doesn't make that easy to do (or it might not provide the APIs to do so at all). I use this as a specific example, but my point is really that hooking up Axios or whatever language model provider API is easy enough because TypeChatLanguageModel just needs a single function at the moment.
Daniel Rosenwasser (@DanielRosenwasser) thete are likely legit n/w level overrides desired, but middleware is likely the better way forward imo rather than anything axios/fetch/ky specific.
I agree with exposing the model the way it is with the single function 👍
Closing as not planned: the current implementation is Fetch-based, so exporting an Axios-specific internal helper no longer fits the API.
The current model API supports proxy configuration through public options and standard proxy environment variables. For a custom transport or provider-specific request parameters, use the documented custom language model interface. This provides an extension point without making Axios part of TypeChat's public API.
Activity
feat export createAxiosLanguageModel microsoft#94
DanielRosenwasser commentedon Aug 9, 2023
Personally I don't think the library should expose Axios at all, since it's an internal implementation detail.
For example, in another issue someone asked about how to take advantage of streaming responses from OpenAI. Best I can tell, Axios doesn't make that easy to do (or it might not provide the APIs to do so at all). I use this as a specific example, but my point is really that hooking up Axios or whatever language model provider API is easy enough because
TypeChatLanguageModeljust needs a single function at the moment.Still, I'll let others weigh in here.
snewell92 commentedon Aug 11, 2023
Daniel Rosenwasser (@DanielRosenwasser) thete are likely legit n/w level overrides desired, but middleware is likely the better way forward imo rather than anything axios/fetch/ky specific.
I agree with exposing the model the way it is with the single function 👍
Akimyou commentedon Aug 14, 2023
I don't think TypeChat needs to provide proxy settings, as it can support proxy access through higher-level configurations, such as proxychains4.
moltar commentedon Aug 15, 2023
trpccan be borrowed, which can adapt to any fetch implementation.robgruen commentedon Oct 12, 2026
Closing as not planned: the current implementation is Fetch-based, so exporting an Axios-specific internal helper no longer fits the API.
The current model API supports proxy configuration through public options and standard proxy environment variables. For a custom transport or provider-specific request parameters, use the documented custom language model interface. This provides an extension point without making Axios part of TypeChat's public API.