responseEncoding is missing from typescript definitions
See original GitHub issueSummary
the responseEncoding
property of the axios config is missing from the AxiosRequestConfig
typescript definitions.
Context
The property is documented in the README but not present in the typescript definitions.
- axios version: v0.18.0
- Environment: node v11.1.0
Issue Analytics
- State:
- Created 5 years ago
- Reactions:10
- Comments:7 (2 by maintainers)
Top Results From Across the Web
ts is missing from the TypeScript compilation. Please make ...
I was migrating from JS into TS simply by renaming a file extension. I was already using Webpack and list of output bundles...
Read more >Azure AD B2C SAML Response encoding issue - Microsoft Q&A
Hi everyone,. If I create a user with a name which does have characters which need to be encoded correctly in the name...
Read more >Content-Encoding - HTTP - MDN Web Docs
Content encoding is mainly used to compress the message data without losing information about the origin media type.
Read more >OGC OpenSearch-EO GeoJSON(-LD) Response Encoding ...
The response encoding defined in the document satisfies the following design ... JSON Schema is a JSON media type for defining the structure...
Read more >Request Config | Axios Docs
... for `responseType` of 'stream' or client-side requests responseEncoding: ... You can also define your proxy using the conventional `http_proxy` and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is still not resolved yet. The PR pointed in the last comment was closed without resolution also.
In case anyone else finds this issue, a workaround to at least be able to compile, is to create a .d.ts in your source and add the following code:
Of course this is not the best “typing” but at least it works until the issue with the types is resolved.
Still an issue with
v 0.19.0