Request utility with validations based on Axios & ts-interface-checker

[!WARNING]
It's fine if you use this library from NPM package with a static versioning in case you want it for some pet-project or to test it's capabilities.

But for production use it's strongly recommended to create a fork, because I do not write Changelogs and may break / add some functionality without notice.

Features

• validates request and response by ts-interface-checker. Checkers could be created using dk-file-generator
• omits extraneous params from response using dk-checker-remove-extraneous
• supports mocks
• supports file downloads if response type is blob with customizable file name
• supports FormData requests
• supports url as function
• supports custom headers
• works in Node.js
• request params starting with omit_ are used in in url creation but omitted in body

Installation

Add dk-request to package.json and install.

Usage

1import { AxiosError } from 'axios';
2import { request, errors } from 'dk-request';
3
4type TypeRequest = {
5  id: string;
6}
7
8type TypeResponse = {
9  data: string;
10}
11
12// possibly auto-generated
13const validators = t.createCheckers({
14  TypeRequest: t.iface([], { id: 'string' }),
15  TypeResponse: t.iface([], { data: 'string' }),
16});
17
18request({
19  url: 'https://google.com/api/get-items',
20  // url: (requestParams) => `https://google.com/api/get-items/${requestParams.id}`,
21  apiName: 'getItems',
22  requestParams: { id: 'id' } as TypeRequest,
23  validatorRequest: validators.TypeRequest,
24  validatorResponse: validators.TypeResponse,
25}).then((response: TypeResponse) => {
26  // response is validated and cleared, put it in store or use as you need
27  
28  successHandler(response);
29}).catch((error: Error | AxiosError) => {
30  // if it's validation error then
31  // error.name === errors.VALIDATION
32  // error.message smth. like 
33  // 'validateRequest: request.id is missing for "getItems"'
34  // 'validateResponse: response.data is not a string for "getItems"'
35  
36  errorHandler(error);
37});

Params

url - string | ((request: any) => string) - full url

apiName - string - just for logging

requestParams - Record<string, any> & { formData?: any; downloadAsFile?: boolean }

If you need to send FormData include it in formData. Other params will not be sent, but could still be used in url function.

If you need to download file passed as blob by backend use downloadAsFile: true, this way response validation will be omitted.

mock (optional) - TypeResponse, there will be no actual request to API, but validations are applied

method (optional, default POST) - 'GET' | 'POST' | 'PUT' | 'DELETE'

headers (optional) - Record<string, any>

extraneousLogger (optional) - logger for dk-checker-remove-extraneous

validatorRequest (optional) - Checker

validatorResponse (optional) - Checker

disableCredentials (optional) - boolean - restrict or allow sending of cookies along with request

omitResponseValidation (optional) - boolean - restrict or allow response validation

afterRequestInterceptor (optional) - (response: AxiosResponse) => Promise<void> - a method for performing some manipulations with response, like checking response.headers (ex. server sends JWT token in headers)

1afterRequestInterceptor: (axiosResponse) => {
2  const newToken = axiosResponse.headers.authorization;
3
4  if (newToken) setTokenToStore(newToken);
5
6  return Promise.resolve();
7}

downloadFileNameGetter (optional) - (response: AxiosResponse) => string - a method for defining custom downloaded file name, ex.

1downloadFileNameGetter: (axiosResponse) => {
2  return (
3    axiosResponse.headers['content-disposition']?.split('filename=')?.[1]?.replaceAll('"', '') ||
4    'result.csv'
5  );
6}

For access to response headers like content-disposition don't forget expose-headers header in server response