This requires TypeScript users to explicitly define the type of the data they
are consuming.

Before this, data was `any` by default. This means TypeScript consumers didn’t
get type safety if they forgot to specify the type.

Technically this is a breaking change for TypeScript users, as this will report
errors if they forgot to specifiy the response type. The simplest workaround
would be to explicitly set the response type to `any`, so it’s not breaking
much.

The `unknown` type is probably a slightly better fit, but this requires
TypeScript ^3.

`data` is still `any` in the very specific use case mentioned in
https://github.com/microsoft/TypeScript/issues/38969Co-authored-by: NJay <jasonsaayman@gmail.com>

* Improved type-safety for AxiosRequestConfig

- AxiosRequestConfig is now a generic type whose template corresponds to data
Signed-off-by: NCarlos Chida <carlos.chida@starchitecture.eu>

* Fixed tests

- TS tests now match the behaviour described in the PR
Signed-off-by: NCarlos Chida <carlos.chida@starchitecture.eu>
Co-authored-by: NJay <jasonsaayman@gmail.com>

* Adding HTTP status code to error.toJSON (axios#2947)

* Adding Error display div to internal server client.html
Co-authored-by: NJay <jasonsaayman@gmail.com>

Co-authored-by: NJay <jasonsaayman@gmail.com>

This patch allows TypeScript users to extend the `Axios` class without
the type checker complaining.

see 7548f2f7Co-authored-by: NJay <jasonsaayman@gmail.com>

Co-authored-by: NJay <jasonsaayman@gmail.com>

Co-authored-by: NJay <jasonsaayman@gmail.com>

* Create SECURITY.md

A simple instruction for security researchers.

* Adding security report email address
Co-authored-by: NJay <jasonsaayman@gmail.com>

Add axios-multi-api to the list
Co-authored-by: NJay <jasonsaayman@gmail.com>

* Fixing README.md

* Update README.md
Co-authored-by: NAsher Hwang <dev@hsh.kr>
Co-authored-by: NAsher Hwang <dev@hsh.kr>
Co-authored-by: NJay <jasonsaayman@gmail.com>

Co-authored-by: NJay <jasonsaayman@gmail.com>

Fixing the example JSON of `Request Config`
Co-authored-by: NJay <jasonsaayman@gmail.com>

Removed un-needed bracket

Updated CI status badge to show Github workflow status

* removed charset setting when setting default header

* Remove charset from tests
Co-authored-by: Nmpark86 <dev.minuk.park@gmail.com>
Co-authored-by: NJay <jasonsaayman@gmail.com>
Co-authored-by: NPilot <timemachine@ctrl-c.club>

Thanks to @socketpair for testing and checking this.

close #3448
Co-authored-by: NJay <jasonsaayman@gmail.com>

Add open collective to repo

* Adding parseInt to config.timeout

* Fixing test message

Co-authored-by: NJay <jasonsaayman@gmail.com>

Previously checking whether a response has exceeded `maxContentLength` was
quadratic with respect to the number of chunks in the response stream and
also caused unnecessary additional memory usage.
Co-authored-by: NJay <jasonsaayman@gmail.com>

* Updating lib/core/README.md :Dispatching requests

* Fixing expression

* Draft

* Added support for primitive types to be converted to JSON if the request Content-Type is 'application/json';
Added throwing SyntaxError if JSON parsing failed and responseType is json;
Added transitional option object;
Added options validator to assert transitional options;
Added transitional option `silentJSONParsing= true` for backward compatibility;
Updated README.md;
Updated typings;

* Fixed isOlderVersion helper;
Fixed typo;
Added validator.spec.js;

* Added forcedJSONParsing transitional option #2791

* `transformData` is now called in the default configuration context if the function context is not specified (for tests compatibility);

* Added `transitional.clarifyTimeoutError` to throw ETIMEDOUT error instead of generic ECONNABORTED on request timeouts;
Added support of onloadend handler if available instead of onreadystatechange;
Added xhr timeout test;
Fixed potential bug of xhr adapter with proper handling timeouts&errors (FakeXMLHTTPRequest failed to handle timeouts);

* Removed unnecessary assertion;

JSON improvements: throw if JSON parsing failed; number, boolean can be passed directly as payload for encoding to JSON #2613, #61, #907 (#3688)

* Draft

* Added support for primitive types to be converted to JSON if the request Content-Type is 'application/json';
Added throwing SyntaxError if JSON parsing failed and responseType is json;
Added transitional option object;
Added options validator to assert transitional options;
Added transitional option `silentJSONParsing= true` for backward compatibility;
Updated README.md;
Updated typings;

* Fixed isOlderVersion helper;
Fixed typo;
Added validator.spec.js;

* Added forcedJSONParsing transitional option #2791

* `transformData` is now called in the default configuration context if the function context is not specified (for tests compatibility);

* Added `transitional.clarifyTimeoutError` to throw ETIMEDOUT error instead of generic ECONNABORTED on request timeouts;
Added support of onloadend handler if available instead of onreadystatechange;
Added xhr timeout test;
Fixed potential bug of xhr adapter with proper handling timeouts&errors (FakeXMLHTTPRequest failed to handle timeouts);

* [Updated] karma sauce launcher which should fix suace tests that are no longer showing as passed and rather completed

* [Updated] karma config to follow es-lint rules of axios

* [Updated] karma version to latest

* [Added] propper browsers when testing local

[Updated] karma sauce launcher which should fix suace tests that are no longer showing as passed and rather completed (#3712)

* Adding ability to omit User-Agent header

* Update line to be more compact

* Add unit tests for user-agent cases
Co-authored-by: NJay <jasonsaayman@gmail.com>

- Tests for transformResponse
 - Remove eslint error by renaming the var
 - Test that there data a length to avoid JSON.parse headache
 - Use `util.isString()` over `typeof`
Co-authored-by: NJay <jasonsaayman@gmail.com>

I have updated the version of follow redirects to see if this will fix a potential memory leak that has been noted by a couple users. This is also being updated to see if it will pass building.

* issue#2609 | Sasha | predictable axios requests

- axios requests are not delayed by pre-emptive promise creation by default
- add options to interceptors api ("synchronous" and "runWhen")
- add documentation and unit tests

* issue#2609 | Sasha | pull request feedback changes

* issue#2609 | Sasha | additional feedback changes

* issue#2609 | Sasha | put back try/catch

* issue#2609 | Sasha | add 2 adapter unit tests

- remove check for requestCancelled
Co-authored-by: Nak71845 <alexandre.korotkov@kroger.com>
Co-authored-by: NXianming Zhong <chinesedfan@qq.com>
Co-authored-by: NJay <jasonsaayman@gmail.com>