The REST client is a high-level client which uses the HTTP client. Its responsibility is to turn a body into a typed resource object.
A 200 will be success.
Redirects (3xx) will be followed.
A 404 will not throw but the result object will be null and the result statusCode will be set.
Other 4xx and 5xx errors will throw. The status code will be attached to the error object. If a RESTful error object is returned ({ message: xxx}), then the error message will be that. Otherwise, it will be a generic, Failed Request: (xxx).
Do you think there might be a security issue?
Have you been phished or identified a security vulnerability?
Please don’t report it here - let us know by sending an email to secure@microsoft.com.
Typed REST and HTTP Client with TypeScript Typings
A lightweight REST and HTTP client optimized for use with TypeScript with generics and async await.
Features
Intellisense and compile support:
Install
Or to install the latest preview:
Samples
See the samples for complete coding examples. Also see the REST and HTTP tests for detailed examples.
Errors
HTTP
The HTTP client does not throw unless truly exceptional.
See HTTP tests for detailed examples.
REST
The REST client is a high-level client which uses the HTTP client. Its responsibility is to turn a body into a typed resource object.
{ message: xxx}), then the error message will be that. Otherwise, it will be a generic,Failed Request: (xxx).See REST tests for detailed examples.
Debugging
To enable detailed console logging of all HTTP requests and responses, set the NODE_DEBUG environment varible:
or
Node support
v2 - [current, maintained] - Supports node 16 and above v1 - End Of Life, for Node < 16, contains security vulnerabilities, use at your own risk
Contributing
To contribute to this repository, see the contribution guide
To build:
To run all tests:
To just run unit tests:
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Security Issues
Do you think there might be a security issue? Have you been phished or identified a security vulnerability? Please don’t report it here - let us know by sending an email to secure@microsoft.com.