Git Product home page Git Product logo

moxios's Introduction

Platinum sponsors

Alloy is the integration development platform that makes it simple and
fast for SaaS companies to launch critical user-facing integrations.

Sign up freeDocumentation



Gold sponsors

API-first authentication, authorization, and fraud prevention

WebsiteDocumentationNode.js Backend SDK

Drag-and-drop authentication, authorization, and identity management

WebsiteDocumentationCommunity




Promise based HTTP client for the browser and node.js

WebsiteDocumentation

npm version CDNJS Build status Gitpod Ready-to-Code code coverage install size npm bundle size npm downloads gitter chat code helpers Known Vulnerabilities

Table of Contents

Features

  • Make XMLHttpRequests from the browser
  • Make http requests from node.js
  • Supports the Promise API
  • Intercept request and response
  • Transform request and response data
  • Cancel requests
  • Automatic transforms for JSON data
  • 🆕 Automatic data object serialization to multipart/form-data and x-www-form-urlencoded body encodings
  • Client side support for protecting against XSRF

Browser Support

Chrome Firefox Safari Opera Edge IE
Latest ✔ Latest ✔ Latest ✔ Latest ✔ Latest ✔ 11 ✔

Browser Matrix

Installing

Package manager

Using npm:

$ npm install axios

Using bower:

$ bower install axios

Using yarn:

$ yarn add axios

Using pnpm:

$ pnpm add axios

Once the package is installed, you can import the library using import or require approach:

import axios, {isCancel, AxiosError} from 'axios';

You can also use the default export, since the named export is just a re-export from the Axios factory:

import axios from 'axios';

console.log(axios.isCancel('something'));

If you use require for importing, only default export is available:

const axios = require('axios');

console.log(axios.isCancel('something'));

For cases where something went wrong when trying to import a module into a custom or legacy environment, you can try importing the module package directly:

const axios = require('axios/dist/browser/axios.cjs'); // browser commonJS bundle (ES2017)
// const axios = require('axios/dist/node/axios.cjs'); // node commonJS bundle (ES2017)

CDN

Using jsDelivr CDN (ES5 UMD browser module):

<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/axios.min.js"></script>

Using unpkg CDN:

<script src="https://unpkg.com/[email protected]/dist/axios.min.js"></script>

Example

Note: CommonJS usage
In order to gain the TypeScript typings (for intellisense / autocomplete) while using CommonJS imports with require(), use the following approach:

import axios from 'axios';
//const axios = require('axios'); // legacy way

// Make a request for a user with a given ID
axios.get('/user?ID=12345')
  .then(function (response) {
    // handle success
    console.log(response);
  })
  .catch(function (error) {
    // handle error
    console.log(error);
  })
  .finally(function () {
    // always executed
  });

// Optionally the request above could also be done as
axios.get('/user', {
    params: {
      ID: 12345
    }
  })
  .then(function (response) {
    console.log(response);
  })
  .catch(function (error) {
    console.log(error);
  })
  .finally(function () {
    // always executed
  });

// Want to use async/await? Add the `async` keyword to your outer function/method.
async function getUser() {
  try {
    const response = await axios.get('/user?ID=12345');
    console.log(response);
  } catch (error) {
    console.error(error);
  }
}

Note: async/await is part of ECMAScript 2017 and is not supported in Internet Explorer and older browsers, so use with caution.

Performing a POST request

axios.post('/user', {
    firstName: 'Fred',
    lastName: 'Flintstone'
  })
  .then(function (response) {
    console.log(response);
  })
  .catch(function (error) {
    console.log(error);
  });

Performing multiple concurrent requests

function getUserAccount() {
  return axios.get('/user/12345');
}

function getUserPermissions() {
  return axios.get('/user/12345/permissions');
}

Promise.all([getUserAccount(), getUserPermissions()])
  .then(function (results) {
    const acct = results[0];
    const perm = results[1];
  });

axios API

Requests can be made by passing the relevant config to axios.

axios(config)
// Send a POST request
axios({
  method: 'post',
  url: '/user/12345',
  data: {
    firstName: 'Fred',
    lastName: 'Flintstone'
  }
});
// GET request for remote image in node.js
axios({
  method: 'get',
  url: 'https://bit.ly/2mTM3nY',
  responseType: 'stream'
})
  .then(function (response) {
    response.data.pipe(fs.createWriteStream('ada_lovelace.jpg'))
  });
axios(url[, config])
// Send a GET request (default method)
axios('/user/12345');

Request method aliases

For convenience, aliases have been provided for all common request methods.

axios.request(config)
axios.get(url[, config])
axios.delete(url[, config])
axios.head(url[, config])
axios.options(url[, config])
axios.post(url[, data[, config]])
axios.put(url[, data[, config]])
axios.patch(url[, data[, config]])
NOTE

When using the alias methods url, method, and data properties don't need to be specified in config.

Concurrency (Deprecated)

Please use Promise.all to replace the below functions.

Helper functions for dealing with concurrent requests.

axios.all(iterable) axios.spread(callback)

Creating an instance

You can create a new instance of axios with a custom config.

axios.create([config])
const instance = axios.create({
  baseURL: 'https://some-domain.com/api/',
  timeout: 1000,
  headers: {'X-Custom-Header': 'foobar'}
});

Instance methods

The available instance methods are listed below. The specified config will be merged with the instance config.

axios#request(config)
axios#get(url[, config])
axios#delete(url[, config])
axios#head(url[, config])
axios#options(url[, config])
axios#post(url[, data[, config]])
axios#put(url[, data[, config]])
axios#patch(url[, data[, config]])
axios#getUri([config])

Request Config

These are the available config options for making requests. Only the url is required. Requests will default to GET if method is not specified.

{
  // `url` is the server URL that will be used for the request
  url: '/user',

  // `method` is the request method to be used when making the request
  method: 'get', // default

  // `baseURL` will be prepended to `url` unless `url` is absolute.
  // It can be convenient to set `baseURL` for an instance of axios to pass relative URLs
  // to methods of that instance.
  baseURL: 'https://some-domain.com/api/',

  // `transformRequest` allows changes to the request data before it is sent to the server
  // This is only applicable for request methods 'PUT', 'POST', 'PATCH' and 'DELETE'
  // The last function in the array must return a string or an instance of Buffer, ArrayBuffer,
  // FormData or Stream
  // You may modify the headers object.
  transformRequest: [function (data, headers) {
    // Do whatever you want to transform the data

    return data;
  }],

  // `transformResponse` allows changes to the response data to be made before
  // it is passed to then/catch
  transformResponse: [function (data) {
    // Do whatever you want to transform the data

    return data;
  }],

  // `headers` are custom headers to be sent
  headers: {'X-Requested-With': 'XMLHttpRequest'},

  // `params` are the URL parameters to be sent with the request
  // Must be a plain object or a URLSearchParams object
  params: {
    ID: 12345
  },
  
  // `paramsSerializer` is an optional config that allows you to customize serializing `params`. 
  paramsSerializer: {

    //Custom encoder function which sends key/value pairs in an iterative fashion.
    encode?: (param: string): string => { /* Do custom operations here and return transformed string */ }, 
    
    // Custom serializer function for the entire parameter. Allows user to mimic pre 1.x behaviour.
    serialize?: (params: Record<string, any>, options?: ParamsSerializerOptions ), 
    
    //Configuration for formatting array indexes in the params. 
    indexes: false // Three available options: (1) indexes: null (leads to no brackets), (2) (default) indexes: false (leads to empty brackets), (3) indexes: true (leads to brackets with indexes).    
  },

  // `data` is the data to be sent as the request body
  // Only applicable for request methods 'PUT', 'POST', 'DELETE , and 'PATCH'
  // When no `transformRequest` is set, must be of one of the following types:
  // - string, plain object, ArrayBuffer, ArrayBufferView, URLSearchParams
  // - Browser only: FormData, File, Blob
  // - Node only: Stream, Buffer, FormData (form-data package)
  data: {
    firstName: 'Fred'
  },

  // syntax alternative to send data into the body
  // method post
  // only the value is sent, not the key
  data: 'Country=Brasil&City=Belo Horizonte',

  // `timeout` specifies the number of milliseconds before the request times out.
  // If the request takes longer than `timeout`, the request will be aborted.
  timeout: 1000, // default is `0` (no timeout)

  // `withCredentials` indicates whether or not cross-site Access-Control requests
  // should be made using credentials
  withCredentials: false, // default

  // `adapter` allows custom handling of requests which makes testing easier.
  // Return a promise and supply a valid response (see lib/adapters/README.md).
  adapter: function (config) {
    /* ... */
  },

  // `auth` indicates that HTTP Basic auth should be used, and supplies credentials.
  // This will set an `Authorization` header, overwriting any existing
  // `Authorization` custom headers you have set using `headers`.
  // Please note that only HTTP Basic auth is configurable through this parameter.
  // For Bearer tokens and such, use `Authorization` custom headers instead.
  auth: {
    username: 'janedoe',
    password: 's00pers3cret'
  },

  // `responseType` indicates the type of data that the server will respond with
  // options are: 'arraybuffer', 'document', 'json', 'text', 'stream'
  //   browser only: 'blob'
  responseType: 'json', // default

  // `responseEncoding` indicates encoding to use for decoding responses (Node.js only)
  // Note: Ignored for `responseType` of 'stream' or client-side requests
  // options are: 'ascii', 'ASCII', 'ansi', 'ANSI', 'binary', 'BINARY', 'base64', 'BASE64', 'base64url',
  // 'BASE64URL', 'hex', 'HEX', 'latin1', 'LATIN1', 'ucs-2', 'UCS-2', 'ucs2', 'UCS2', 'utf-8', 'UTF-8',
  // 'utf8', 'UTF8', 'utf16le', 'UTF16LE'
  responseEncoding: 'utf8', // default

  // `xsrfCookieName` is the name of the cookie to use as a value for xsrf token
  xsrfCookieName: 'XSRF-TOKEN', // default

  // `xsrfHeaderName` is the name of the http header that carries the xsrf token value
  xsrfHeaderName: 'X-XSRF-TOKEN', // default
    
  // `undefined` (default) - set XSRF header only for the same origin requests
  withXSRFToken: boolean | undefined | ((config: InternalAxiosRequestConfig) => boolean | undefined),

  // `onUploadProgress` allows handling of progress events for uploads
  // browser & node.js
  onUploadProgress: function ({loaded, total, progress, bytes, estimated, rate, upload = true}) {
    // Do whatever you want with the Axios progress event
  },

  // `onDownloadProgress` allows handling of progress events for downloads
  // browser & node.js
  onDownloadProgress: function ({loaded, total, progress, bytes, estimated, rate, download = true}) {
    // Do whatever you want with the Axios progress event
  },

  // `maxContentLength` defines the max size of the http response content in bytes allowed in node.js
  maxContentLength: 2000,

  // `maxBodyLength` (Node only option) defines the max size of the http request content in bytes allowed
  maxBodyLength: 2000,

  // `validateStatus` defines whether to resolve or reject the promise for a given
  // HTTP response status code. If `validateStatus` returns `true` (or is set to `null`
  // or `undefined`), the promise will be resolved; otherwise, the promise will be
  // rejected.
  validateStatus: function (status) {
    return status >= 200 && status < 300; // default
  },

  // `maxRedirects` defines the maximum number of redirects to follow in node.js.
  // If set to 0, no redirects will be followed.
  maxRedirects: 21, // default

  // `beforeRedirect` defines a function that will be called before redirect.
  // Use this to adjust the request options upon redirecting,
  // to inspect the latest response headers,
  // or to cancel the request by throwing an error
  // If maxRedirects is set to 0, `beforeRedirect` is not used.
  beforeRedirect: (options, { headers }) => {
    if (options.hostname === "example.com") {
      options.auth = "user:password";
    }
  },

  // `socketPath` defines a UNIX Socket to be used in node.js.
  // e.g. '/var/run/docker.sock' to send requests to the docker daemon.
  // Only either `socketPath` or `proxy` can be specified.
  // If both are specified, `socketPath` is used.
  socketPath: null, // default
  
  // `transport` determines the transport method that will be used to make the request. If defined, it will be used. Otherwise, if `maxRedirects` is 0, the default `http` or `https` library will be used, depending on the protocol specified in `protocol`. Otherwise, the `httpFollow` or `httpsFollow` library will be used, again depending on the protocol, which can handle redirects.
  transport: undefined, // default

  // `httpAgent` and `httpsAgent` define a custom agent to be used when performing http
  // and https requests, respectively, in node.js. This allows options to be added like
  // `keepAlive` that are not enabled by default.
  httpAgent: new http.Agent({ keepAlive: true }),
  httpsAgent: new https.Agent({ keepAlive: true }),

  // `proxy` defines the hostname, port, and protocol of the proxy server.
  // You can also define your proxy using the conventional `http_proxy` and
  // `https_proxy` environment variables. If you are using environment variables
  // for your proxy configuration, you can also define a `no_proxy` environment
  // variable as a comma-separated list of domains that should not be proxied.
  // Use `false` to disable proxies, ignoring environment variables.
  // `auth` indicates that HTTP Basic auth should be used to connect to the proxy, and
  // supplies credentials.
  // This will set an `Proxy-Authorization` header, overwriting any existing
  // `Proxy-Authorization` custom headers you have set using `headers`.
  // If the proxy server uses HTTPS, then you must set the protocol to `https`.
  proxy: {
    protocol: 'https',
    host: '127.0.0.1',
    // hostname: '127.0.0.1' // Takes precedence over 'host' if both are defined
    port: 9000,
    auth: {
      username: 'mikeymike',
      password: 'rapunz3l'
    }
  },

  // `cancelToken` specifies a cancel token that can be used to cancel the request
  // (see Cancellation section below for details)
  cancelToken: new CancelToken(function (cancel) {
  }),

  // an alternative way to cancel Axios requests using AbortController
  signal: new AbortController().signal,

  // `decompress` indicates whether or not the response body should be decompressed
  // automatically. If set to `true` will also remove the 'content-encoding' header
  // from the responses objects of all decompressed responses
  // - Node only (XHR cannot turn off decompression)
  decompress: true, // default

  // `insecureHTTPParser` boolean.
  // Indicates where to use an insecure HTTP parser that accepts invalid HTTP headers.
  // This may allow interoperability with non-conformant HTTP implementations.
  // Using the insecure parser should be avoided.
  // see options https://nodejs.org/dist/latest-v12.x/docs/api/http.html#http_http_request_url_options_callback
  // see also https://nodejs.org/en/blog/vulnerability/february-2020-security-releases/#strict-http-header-parsing-none
  insecureHTTPParser: undefined, // default

  // transitional options for backward compatibility that may be removed in the newer versions
  transitional: {
    // silent JSON parsing mode
    // `true`  - ignore JSON parsing errors and set response.data to null if parsing failed (old behaviour)
    // `false` - throw SyntaxError if JSON parsing failed (Note: responseType must be set to 'json')
    silentJSONParsing: true, // default value for the current Axios version

    // try to parse the response string as JSON even if `responseType` is not 'json'
    forcedJSONParsing: true,

    // throw ETIMEDOUT error instead of generic ECONNABORTED on request timeouts
    clarifyTimeoutError: false,
  },

  env: {
    // The FormData class to be used to automatically serialize the payload into a FormData object
    FormData: window?.FormData || global?.FormData
  },

  formSerializer: {
      visitor: (value, key, path, helpers) => {}; // custom visitor function to serialize form values
      dots: boolean; // use dots instead of brackets format
      metaTokens: boolean; // keep special endings like {} in parameter key
      indexes: boolean; // array indexes format null - no brackets, false - empty brackets, true - brackets with indexes
  },

  // http adapter only (node.js)
  maxRate: [
    100 * 1024, // 100KB/s upload limit,
    100 * 1024  // 100KB/s download limit
  ]
}

Response Schema

The response for a request contains the following information.

{
  // `data` is the response that was provided by the server
  data: {},

  // `status` is the HTTP status code from the server response
  status: 200,

  // `statusText` is the HTTP status message from the server response
  statusText: 'OK',

  // `headers` the HTTP headers that the server responded with
  // All header names are lowercase and can be accessed using the bracket notation.
  // Example: `response.headers['content-type']`
  headers: {},

  // `config` is the config that was provided to `axios` for the request
  config: {},

  // `request` is the request that generated this response
  // It is the last ClientRequest instance in node.js (in redirects)
  // and an XMLHttpRequest instance in the browser
  request: {}
}

When using then, you will receive the response as follows:

axios.get('/user/12345')
  .then(function (response) {
    console.log(response.data);
    console.log(response.status);
    console.log(response.statusText);
    console.log(response.headers);
    console.log(response.config);
  });

When using catch, or passing a rejection callback as second parameter of then, the response will be available through the error object as explained in the Handling Errors section.

Config Defaults

You can specify config defaults that will be applied to every request.

Global axios defaults

axios.defaults.baseURL = 'https://api.example.com';

// Important: If axios is used with multiple domains, the AUTH_TOKEN will be sent to all of them.
// See below for an example using Custom instance defaults instead.
axios.defaults.headers.common['Authorization'] = AUTH_TOKEN;

axios.defaults.headers.post['Content-Type'] = 'application/x-www-form-urlencoded';

Custom instance defaults

// Set config defaults when creating the instance
const instance = axios.create({
  baseURL: 'https://api.example.com'
});

// Alter defaults after instance has been created
instance.defaults.headers.common['Authorization'] = AUTH_TOKEN;

Config order of precedence

Config will be merged with an order of precedence. The order is library defaults found in lib/defaults.js, then defaults property of the instance, and finally config argument for the request. The latter will take precedence over the former. Here's an example.

// Create an instance using the config defaults provided by the library
// At this point the timeout config value is `0` as is the default for the library
const instance = axios.create();

// Override timeout default for the library
// Now all requests using this instance will wait 2.5 seconds before timing out
instance.defaults.timeout = 2500;

// Override timeout for this request as it's known to take a long time
instance.get('/longRequest', {
  timeout: 5000
});

Interceptors

You can intercept requests or responses before they are handled by then or catch.

// Add a request interceptor
axios.interceptors.request.use(function (config) {
    // Do something before request is sent
    return config;
  }, function (error) {
    // Do something with request error
    return Promise.reject(error);
  });

// Add a response interceptor
axios.interceptors.response.use(function (response) {
    // Any status code that lie within the range of 2xx cause this function to trigger
    // Do something with response data
    return response;
  }, function (error) {
    // Any status codes that falls outside the range of 2xx cause this function to trigger
    // Do something with response error
    return Promise.reject(error);
  });

If you need to remove an interceptor later you can.

const myInterceptor = axios.interceptors.request.use(function () {/*...*/});
axios.interceptors.request.eject(myInterceptor);

You can also clear all interceptors for requests or responses.

const instance = axios.create();
instance.interceptors.request.use(function () {/*...*/});
instance.interceptors.request.clear(); // Removes interceptors from requests
instance.interceptors.response.use(function () {/*...*/});
instance.interceptors.response.clear(); // Removes interceptors from responses

You can add interceptors to a custom instance of axios.

const instance = axios.create();
instance.interceptors.request.use(function () {/*...*/});

When you add request interceptors, they are presumed to be asynchronous by default. This can cause a delay in the execution of your axios request when the main thread is blocked (a promise is created under the hood for the interceptor and your request gets put on the bottom of the call stack). If your request interceptors are synchronous you can add a flag to the options object that will tell axios to run the code synchronously and avoid any delays in request execution.

axios.interceptors.request.use(function (config) {
  config.headers.test = 'I am only a header!';
  return config;
}, null, { synchronous: true });

If you want to execute a particular interceptor based on a runtime check, you can add a runWhen function to the options object. The interceptor will not be executed if and only if the return of runWhen is false. The function will be called with the config object (don't forget that you can bind your own arguments to it as well.) This can be handy when you have an asynchronous request interceptor that only needs to run at certain times.

function onGetCall(config) {
  return config.method === 'get';
}
axios.interceptors.request.use(function (config) {
  config.headers.test = 'special get headers';
  return config;
}, null, { runWhen: onGetCall });

Multiple Interceptors

Given you add multiple response interceptors and when the response was fulfilled

  • then each interceptor is executed
  • then they are executed in the order they were added
  • then only the last interceptor's result is returned
  • then every interceptor receives the result of its predecessor
  • and when the fulfillment-interceptor throws
    • then the following fulfillment-interceptor is not called
    • then the following rejection-interceptor is called
    • once caught, another following fulfill-interceptor is called again (just like in a promise chain).

Read the interceptor tests for seeing all this in code.

Error Types

There are many different axios error messages that can appear that can provide basic information about the specifics of the error and where opportunities may lie in debugging.

The general structure of axios errors is as follows:

Property Definition
message A quick summary of the error message and the status it failed with.
name This defines where the error originated from. For axios, it will always be an 'AxiosError'.
stack Provides the stack trace of the error.
config An axios config object with specific instance configurations defined by the user from when the request was made
code Represents an axios identified error. The table below lists out specific definitions for internal axios error.
status HTTP response status code. See here for common HTTP response status code meanings.

Below is a list of potential axios identified error

Code Definition
ERR_BAD_OPTION_VALUE Invalid or unsupported value provided in axios configuration.
ERR_BAD_OPTION Invalid option provided in axios configuration.
ECONNABORTED Request timed out due to exceeding timeout specified in axios configuration.
ETIMEDOUT Request timed out due to exceeding default axios timelimit.
ERR_NETWORK Network-related issue.
ERR_FR_TOO_MANY_REDIRECTS Request is redirected too many times; exceeds max redirects specified in axios configuration.
ERR_DEPRECATED Deprecated feature or method used in axios.
ERR_BAD_RESPONSE Response cannot be parsed properly or is in an unexpected format.
ERR_BAD_REQUEST Requested has unexpected format or missing required parameters.
ERR_CANCELED Feature or method is canceled explicitly by the user.
ERR_NOT_SUPPORT Feature or method not supported in the current axios environment.
ERR_INVALID_URL Invalid URL provided for axios request.

Handling Errors

the default behavior is to reject every response that returns with a status code that falls out of the range of 2xx and treat it as an error.

axios.get('/user/12345')
  .catch(function (error) {
    if (error.response) {
      // The request was made and the server responded with a status code
      // that falls out of the range of 2xx
      console.log(error.response.data);
      console.log(error.response.status);
      console.log(error.response.headers);
    } else if (error.request) {
      // The request was made but no response was received
      // `error.request` is an instance of XMLHttpRequest in the browser and an instance of
      // http.ClientRequest in node.js
      console.log(error.request);
    } else {
      // Something happened in setting up the request that triggered an Error
      console.log('Error', error.message);
    }
    console.log(error.config);
  });

Using the validateStatus config option, you can override the default condition (status >= 200 && status < 300) and define HTTP code(s) that should throw an error.

axios.get('/user/12345', {
  validateStatus: function (status) {
    return status < 500; // Resolve only if the status code is less than 500
  }
})

Using toJSON you get an object with more information about the HTTP error.

axios.get('/user/12345')
  .catch(function (error) {
    console.log(error.toJSON());
  });

Cancellation

AbortController

Starting from v0.22.0 Axios supports AbortController to cancel requests in fetch API way:

const controller = new AbortController();

axios.get('/foo/bar', {
   signal: controller.signal
}).then(function(response) {
   //...
});
// cancel the request
controller.abort()

CancelToken 👎deprecated

You can also cancel a request using a CancelToken.

The axios cancel token API is based on the withdrawn cancellable promises proposal.

This API is deprecated since v0.22.0 and shouldn't be used in new projects

You can create a cancel token using the CancelToken.source factory as shown below:

const CancelToken = axios.CancelToken;
const source = CancelToken.source();

axios.get('/user/12345', {
  cancelToken: source.token
}).catch(function (thrown) {
  if (axios.isCancel(thrown)) {
    console.log('Request canceled', thrown.message);
  } else {
    // handle error
  }
});

axios.post('/user/12345', {
  name: 'new name'
}, {
  cancelToken: source.token
})

// cancel the request (the message parameter is optional)
source.cancel('Operation canceled by the user.');

You can also create a cancel token by passing an executor function to the CancelToken constructor:

const CancelToken = axios.CancelToken;
let cancel;

axios.get('/user/12345', {
  cancelToken: new CancelToken(function executor(c) {
    // An executor function receives a cancel function as a parameter
    cancel = c;
  })
});

// cancel the request
cancel();

Note: you can cancel several requests with the same cancel token/abort controller. If a cancellation token is already cancelled at the moment of starting an Axios request, then the request is cancelled immediately, without any attempts to make a real request.

During the transition period, you can use both cancellation APIs, even for the same request:

Using application/x-www-form-urlencoded format

URLSearchParams

By default, axios serializes JavaScript objects to JSON. To send data in the application/x-www-form-urlencoded format instead, you can use the URLSearchParams API, which is supported in the vast majority of browsers,and Node starting with v10 (released in 2018).

const params = new URLSearchParams({ foo: 'bar' });
params.append('extraparam', 'value');
axios.post('/foo', params);

Query string (Older browsers)

For compatibility with very old browsers, there is a polyfill available (make sure to polyfill the global environment).

Alternatively, you can encode data using the qs library:

const qs = require('qs');
axios.post('/foo', qs.stringify({ 'bar': 123 }));

Or in another way (ES6),

import qs from 'qs';
const data = { 'bar': 123 };
const options = {
  method: 'POST',
  headers: { 'content-type': 'application/x-www-form-urlencoded' },
  data: qs.stringify(data),
  url,
};
axios(options);

Older Node.js versions

For older Node.js engines, you can use the querystring module as follows:

const querystring = require('querystring');
axios.post('https://something.com/', querystring.stringify({ foo: 'bar' }));

You can also use the qs library.

Note: The qs library is preferable if you need to stringify nested objects, as the querystring method has known issues with that use case.

🆕 Automatic serialization to URLSearchParams

Axios will automatically serialize the data object to urlencoded format if the content-type header is set to "application/x-www-form-urlencoded".

const data = {
  x: 1,
  arr: [1, 2, 3],
  arr2: [1, [2], 3],
  users: [{name: 'Peter', surname: 'Griffin'}, {name: 'Thomas', surname: 'Anderson'}],
};

await axios.postForm('https://postman-echo.com/post', data,
  {headers: {'content-type': 'application/x-www-form-urlencoded'}}
);

The server will handle it as:

  {
    x: '1',
    'arr[]': [ '1', '2', '3' ],
    'arr2[0]': '1',
    'arr2[1][0]': '2',
    'arr2[2]': '3',
    'arr3[]': [ '1', '2', '3' ],
    'users[0][name]': 'Peter',
    'users[0][surname]': 'griffin',
    'users[1][name]': 'Thomas',
    'users[1][surname]': 'Anderson'
  }

If your backend body-parser (like body-parser of express.js) supports nested objects decoding, you will get the same object on the server-side automatically

  var app = express();

  app.use(bodyParser.urlencoded({ extended: true })); // support encoded bodies

  app.post('/', function (req, res, next) {
     // echo body as JSON
     res.send(JSON.stringify(req.body));
  });

  server = app.listen(3000);

Using multipart/form-data format

FormData

To send the data as a multipart/formdata you need to pass a formData instance as a payload. Setting the Content-Type header is not required as Axios guesses it based on the payload type.

const formData = new FormData();
formData.append('foo', 'bar');

axios.post('https://httpbin.org/post', formData);

In node.js, you can use the form-data library as follows:

const FormData = require('form-data');

const form = new FormData();
form.append('my_field', 'my value');
form.append('my_buffer', new Buffer(10));
form.append('my_file', fs.createReadStream('/foo/bar.jpg'));

axios.post('https://example.com', form)

🆕 Automatic serialization to FormData

Starting from v0.27.0, Axios supports automatic object serialization to a FormData object if the request Content-Type header is set to multipart/form-data.

The following request will submit the data in a FormData format (Browser & Node.js):

import axios from 'axios';

axios.post('https://httpbin.org/post', {x: 1}, {
  headers: {
    'Content-Type': 'multipart/form-data'
  }
}).then(({data}) => console.log(data));

In the node.js build, the (form-data) polyfill is used by default.

You can overload the FormData class by setting the env.FormData config variable, but you probably won't need it in most cases:

const axios = require('axios');
var FormData = require('form-data');

axios.post('https://httpbin.org/post', {x: 1, buf: new Buffer(10)}, {
  headers: {
    'Content-Type': 'multipart/form-data'
  }
}).then(({data}) => console.log(data));

Axios FormData serializer supports some special endings to perform the following operations:

  • {} - serialize the value with JSON.stringify
  • [] - unwrap the array-like object as separate fields with the same key

Note: unwrap/expand operation will be used by default on arrays and FileList objects

FormData serializer supports additional options via config.formSerializer: object property to handle rare cases:

  • visitor: Function - user-defined visitor function that will be called recursively to serialize the data object to a FormData object by following custom rules.

  • dots: boolean = false - use dot notation instead of brackets to serialize arrays and objects;

  • metaTokens: boolean = true - add the special ending (e.g user{}: '{"name": "John"}') in the FormData key. The back-end body-parser could potentially use this meta-information to automatically parse the value as JSON.

  • indexes: null|false|true = false - controls how indexes will be added to unwrapped keys of flat array-like objects

    • null - don't add brackets (arr: 1, arr: 2, arr: 3)
    • false(default) - add empty brackets (arr[]: 1, arr[]: 2, arr[]: 3)
    • true - add brackets with indexes (arr[0]: 1, arr[1]: 2, arr[2]: 3)

Let's say we have an object like this one:

const obj = {
  x: 1,
  arr: [1, 2, 3],
  arr2: [1, [2], 3],
  users: [{name: 'Peter', surname: 'Griffin'}, {name: 'Thomas', surname: 'Anderson'}],
  'obj2{}': [{x:1}]
};

The following steps will be executed by the Axios serializer internally:

const formData = new FormData();
formData.append('x', '1');
formData.append('arr[]', '1');
formData.append('arr[]', '2');
formData.append('arr[]', '3');
formData.append('arr2[0]', '1');
formData.append('arr2[1][0]', '2');
formData.append('arr2[2]', '3');
formData.append('users[0][name]', 'Peter');
formData.append('users[0][surname]', 'Griffin');
formData.append('users[1][name]', 'Thomas');
formData.append('users[1][surname]', 'Anderson');
formData.append('obj2{}', '[{"x":1}]');

Axios supports the following shortcut methods: postForm, putForm, patchForm which are just the corresponding http methods with the Content-Type header preset to multipart/form-data.

Files Posting

You can easily submit a single file:

await axios.postForm('https://httpbin.org/post', {
  'myVar' : 'foo',
  'file': document.querySelector('#fileInput').files[0]
});

or multiple files as multipart/form-data:

await axios.postForm('https://httpbin.org/post', {
  'files[]': document.querySelector('#fileInput').files
});

FileList object can be passed directly:

await axios.postForm('https://httpbin.org/post', document.querySelector('#fileInput').files)

All files will be sent with the same field names: files[].

🆕 HTML Form Posting (browser)

Pass HTML Form element as a payload to submit it as multipart/form-data content.

await axios.postForm('https://httpbin.org/post', document.querySelector('#htmlForm'));

FormData and HTMLForm objects can also be posted as JSON by explicitly setting the Content-Type header to application/json:

await axios.post('https://httpbin.org/post', document.querySelector('#htmlForm'), {
  headers: {
    'Content-Type': 'application/json'
  }
})

For example, the Form

<form id="form">
  <input type="text" name="foo" value="1">
  <input type="text" name="deep.prop" value="2">
  <input type="text" name="deep prop spaced" value="3">
  <input type="text" name="baz" value="4">
  <input type="text" name="baz" value="5">

  <select name="user.age">
    <option value="value1">Value 1</option>
    <option value="value2" selected>Value 2</option>
    <option value="value3">Value 3</option>
  </select>

  <input type="submit" value="Save">
</form>

will be submitted as the following JSON object:

{
  "foo": "1",
  "deep": {
    "prop": {
      "spaced": "3"
    }
  },
  "baz": [
    "4",
    "5"
  ],
  "user": {
    "age": "value2"
  }
}

Sending Blobs/Files as JSON (base64) is not currently supported.

🆕 Progress capturing

Axios supports both browser and node environments to capture request upload/download progress.

await axios.post(url, data, {
  onUploadProgress: function (axiosProgressEvent) {
    /*{
      loaded: number;
      total?: number;
      progress?: number; // in range [0..1]
      bytes: number; // how many bytes have been transferred since the last trigger (delta)
      estimated?: number; // estimated time in seconds
      rate?: number; // upload speed in bytes
      upload: true; // upload sign
    }*/
  },

  onDownloadProgress: function (axiosProgressEvent) {
    /*{
      loaded: number;
      total?: number;
      progress?: number;
      bytes: number; 
      estimated?: number;
      rate?: number; // download speed in bytes
      download: true; // download sign
    }*/
  }
});  

You can also track stream upload/download progress in node.js:

const {data} = await axios.post(SERVER_URL, readableStream, {
   onUploadProgress: ({progress}) => {
     console.log((progress * 100).toFixed(2));
   },
  
   headers: {
    'Content-Length': contentLength
   },

   maxRedirects: 0 // avoid buffering the entire stream
});

Note: Capturing FormData upload progress is not currently supported in node.js environments.

⚠️ Warning It is recommended to disable redirects by setting maxRedirects: 0 to upload the stream in the node.js environment, as follow-redirects package will buffer the entire stream in RAM without following the "backpressure" algorithm.

🆕 Rate limiting

Download and upload rate limits can only be set for the http adapter (node.js):

const {data} = await axios.post(LOCAL_SERVER_URL, myBuffer, {
  onUploadProgress: ({progress, rate}) => {
    console.log(`Upload [${(progress*100).toFixed(2)}%]: ${(rate / 1024).toFixed(2)}KB/s`)
  },
   
  maxRate: [100 * 1024], // 100KB/s limit
});

🆕 AxiosHeaders

Axios has its own AxiosHeaders class to manipulate headers using a Map-like API that guarantees caseless work. Although HTTP is case-insensitive in headers, Axios will retain the case of the original header for stylistic reasons and for a workaround when servers mistakenly consider the header's case. The old approach of directly manipulating headers object is still available, but deprecated and not recommended for future usage.

Working with headers

An AxiosHeaders object instance can contain different types of internal values. that control setting and merging logic. The final headers object with string values is obtained by Axios by calling the toJSON method.

Note: By JSON here we mean an object consisting only of string values intended to be sent over the network.

The header value can be one of the following types:

  • string - normal string value that will be sent to the server
  • null - skip header when rendering to JSON
  • false - skip header when rendering to JSON, additionally indicates that set method must be called with rewrite option set to true to overwrite this value (Axios uses this internally to allow users to opt out of installing certain headers like User-Agent or Content-Type)
  • undefined - value is not set

Note: The header value is considered set if it is not equal to undefined.

The headers object is always initialized inside interceptors and transformers:

  axios.interceptors.request.use((request: InternalAxiosRequestConfig) => {
      request.headers.set('My-header', 'value');

      request.headers.set({
        "My-set-header1": "my-set-value1",
        "My-set-header2": "my-set-value2"
      });
      
      request.headers.set('User-Agent', false); // disable subsequent setting the header by Axios

      request.headers.setContentType('text/plain');
    
      request.headers['My-set-header2'] = 'newValue' // direct access is deprecated
    
      return request;
    }
  );

You can iterate over an AxiosHeaders instance using a for...of statement:

const headers = new AxiosHeaders({
  foo: '1',
  bar: '2',
  baz: '3'
});

for(const [header, value] of headers) {
  console.log(header, value);
}

// foo 1
// bar 2
// baz 3

new AxiosHeaders(headers?)

Constructs a new AxiosHeaders instance.

constructor(headers?: RawAxiosHeaders | AxiosHeaders | string);

If the headers object is a string, it will be parsed as RAW HTTP headers.

const headers = new AxiosHeaders(`
Host: www.bing.com
User-Agent: curl/7.54.0
Accept: */*`);

console.log(headers);

// Object [AxiosHeaders] {
//   host: 'www.bing.com',
//   'user-agent': 'curl/7.54.0',
//   accept: '*/*'
// }

AxiosHeaders#set

set(headerName, value: Axios, rewrite?: boolean);
set(headerName, value, rewrite?: (this: AxiosHeaders, value: string, name: string, headers: RawAxiosHeaders) => boolean);
set(headers?: RawAxiosHeaders | AxiosHeaders | string, rewrite?: boolean);

The rewrite argument controls the overwriting behavior:

  • false - do not overwrite if header's value is set (is not undefined)
  • undefined (default) - overwrite the header unless its value is set to false
  • true - rewrite anyway

The option can also accept a user-defined function that determines whether the value should be overwritten or not.

Returns this.

AxiosHeaders#get(header)

  get(headerName: string, matcher?: true | AxiosHeaderMatcher): AxiosHeaderValue;
  get(headerName: string, parser: RegExp): RegExpExecArray | null;

Returns the internal value of the header. It can take an extra argument to parse the header's value with RegExp.exec, matcher function or internal key-value parser.

const headers = new AxiosHeaders({
  'Content-Type': 'multipart/form-data; boundary=Asrf456BGe4h'
});

console.log(headers.get('Content-Type')); 
// multipart/form-data; boundary=Asrf456BGe4h

console.log(headers.get('Content-Type', true)); // parse key-value pairs from a string separated with \s,;= delimiters:
// [Object: null prototype] {
//   'multipart/form-data': undefined,
//    boundary: 'Asrf456BGe4h'
// }


console.log(headers.get('Content-Type', (value, name, headers) => {
  return String(value).replace(/a/g, 'ZZZ');
}));
// multipZZZrt/form-dZZZtZZZ; boundZZZry=Asrf456BGe4h

console.log(headers.get('Content-Type', /boundary=(\w+)/)?.[0]);
// boundary=Asrf456BGe4h

Returns the value of the header.

AxiosHeaders#has(header, matcher?)

has(header: string, matcher?: AxiosHeaderMatcher): boolean;

Returns true if the header is set (has no undefined value).

AxiosHeaders#delete(header, matcher?)

delete(header: string | string[], matcher?: AxiosHeaderMatcher): boolean;

Returns true if at least one header has been removed.

AxiosHeaders#clear(matcher?)

clear(matcher?: AxiosHeaderMatcher): boolean;

Removes all headers. Unlike the delete method matcher, this optional matcher will be used to match against the header name rather than the value.

const headers = new AxiosHeaders({
  'foo': '1',
  'x-foo': '2',
  'x-bar': '3',
});

console.log(headers.clear(/^x-/)); // true

console.log(headers.toJSON()); // [Object: null prototype] { foo: '1' }

Returns true if at least one header has been cleared.

AxiosHeaders#normalize(format);

If the headers object was changed directly, it can have duplicates with the same name but in different cases. This method normalizes the headers object by combining duplicate keys into one. Axios uses this method internally after calling each interceptor. Set format to true for converting headers name to lowercase and capitalize the initial letters (cOntEnt-type => Content-Type)

const headers = new AxiosHeaders({
  'foo': '1',
});

headers.Foo = '2';
headers.FOO = '3';

console.log(headers.toJSON()); // [Object: null prototype] { foo: '1', Foo: '2', FOO: '3' }
console.log(headers.normalize().toJSON()); // [Object: null prototype] { foo: '3' }
console.log(headers.normalize(true).toJSON()); // [Object: null prototype] { Foo: '3' }

Returns this.

AxiosHeaders#concat(...targets)

concat(...targets: Array<AxiosHeaders | RawAxiosHeaders | string | undefined | null>): AxiosHeaders;

Merges the instance with targets into a new AxiosHeaders instance. If the target is a string, it will be parsed as RAW HTTP headers.

Returns a new AxiosHeaders instance.

AxiosHeaders#toJSON(asStrings?)

toJSON(asStrings?: boolean): RawAxiosHeaders;

Resolve all internal headers values into a new null prototype object. Set asStrings to true to resolve arrays as a string containing all elements, separated by commas.

AxiosHeaders.from(thing?)

from(thing?: AxiosHeaders | RawAxiosHeaders | string): AxiosHeaders;

Returns a new AxiosHeaders instance created from the raw headers passed in, or simply returns the given headers object if it's an AxiosHeaders instance.

AxiosHeaders.concat(...targets)

concat(...targets: Array<AxiosHeaders | RawAxiosHeaders | string | undefined | null>): AxiosHeaders;

Returns a new AxiosHeaders instance created by merging the target objects.

Shortcuts

The following shortcuts are available:

  • setContentType, getContentType, hasContentType

  • setContentLength, getContentLength, hasContentLength

  • setAccept, getAccept, hasAccept

  • setUserAgent, getUserAgent, hasUserAgent

  • setContentEncoding, getContentEncoding, hasContentEncoding

Semver

Until axios reaches a 1.0 release, breaking changes will be released with a new minor version. For example 0.5.1, and 0.5.4 will have the same API, but 0.6.0 will have breaking changes.

Promises

axios depends on a native ES6 Promise implementation to be supported. If your environment doesn't support ES6 Promises, you can polyfill.

TypeScript

axios includes TypeScript definitions and a type guard for axios errors.

let user: User = null;
try {
  const { data } = await axios.get('/user?ID=12345');
  user = data.userDetails;
} catch (error) {
  if (axios.isAxiosError(error)) {
    handleAxiosError(error);
  } else {
    handleUnexpectedError(error);
  }
}

Because axios dual publishes with an ESM default export and a CJS module.exports, there are some caveats. The recommended setting is to use "moduleResolution": "node16" (this is implied by "module": "node16"). Note that this requires TypeScript 4.7 or greater. If use ESM, your settings should be fine. If you compile TypeScript to CJS and you can’t use "moduleResolution": "node 16", you have to enable esModuleInterop. If you use TypeScript to type check CJS JavaScript code, your only option is to use "moduleResolution": "node16".

Online one-click setup

You can use Gitpod, an online IDE(which is free for Open Source) for contributing or running the examples online.

Open in Gitpod

Resources

Credits

axios is heavily inspired by the $http service provided in AngularJS. Ultimately axios is an effort to provide a standalone $http-like service for use outside of AngularJS.

License

MIT

moxios's People

Contributors

alshakero avatar amilajack avatar dependabot[bot] avatar doshinirav avatar drasky-vanderhoff avatar dtryon avatar falconmick avatar hovissimo avatar jakxz avatar jasonsaayman avatar mzabriskie avatar nicangeli avatar paperbackdragon avatar pawel-schmidt avatar tobbe avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

moxios's Issues

How to mock reject reponse with status > 400

How to mock reject reponse with status > 400 .
I want to mock errorneous response i.g.

      moxios.wait(() => {
        const request = moxios.requests.mostRecent();
        request.respondWith({
          status: 422,
          response: { message: 'problem' },
        });
      });

How can I do it?

Can't seem to use the baseURL defined in Axios default configuration

For context, I'm using TypeScript, React and Jest with Enzyme.

On my application I'm doing something like this:

import * as React from "react";

import Axios from "axios";

export default class Application extends React.Component<any, any> {

    public constructor() {
        super();

        Axios.defaults.baseURL = "https://hostname.herokuapp.com";
    }

    public componentWillMount(): void {
        Axios.get("/token")
            .then((response) => {
                console.log(response);
            });
    }

}

And I'm trying to stub the /token request like this:

import * as React from "react";
import * as Moxios from "moxios";

import { shallow } from "enzyme";

import Application from "components/Application";

describe("Application", () => {

    Moxios.install();

    test("something", () => {
        shallow(<Application />);

        Moxios.stubRequest("/token", {
            status: 200,
            response: {
                message: "Hello Axios"
            }
        });
    });

});

The console.log(response); should output my mocked response, but it's not. However, if I change the stubRequest call to:

Moxios.stubRequest("https://hostname.herokuapp.com/token", ...);

It works... But that kinda defeats the purpose of the baseURL property. Well, it works on the code so that's not too bad, but why is it not working on testing too?

I've tried I've also tried this:

Moxios.install(Axios.create({
    baseURL: "https://hostname.herokuapp.com"
}));

But it didn't work...

What am I missing?

How can i mock only urls with specific pattern.

How can i achieve the following case:

I want moxios adapter to be set only in particular url patterns.
Other url patterns should have axios default adapter.

I was able to change moxios adapter either for all urls used by axios or none of them.

Can this be achieved or is it a bad practice?

DEFAULT_WAIT_DELAY probably too big

Individual tests are taking too long to complete, and I have to set delay to zero manualy.
Maybe it's better to set this delay to 0 by default?

Create new build with stubtimeout

I'm trying to use stubtimeout in version 0.3.0 but it doesn't seem to be included in the dist files.

Am I missing something or is it not present in the build of 0.3.0?

Installing/Uninstalling like the README states doesn't mock requests properly

I've tried to follow the documentation but for some reason can't get this ti work properly. If relevant, I'm using TypeScript, React and Jest with Enzyme.

I have something like this on my app:

public componentWillMount(): void {
    Axios.get("https://hostname/token")
        .then((response) => {
            console.log(response);
        })
        .catch((error) => {
            console.log(error);
        });
}

And this is my simple test spec:

import * as React from "react";
import * as Moxios from "moxios";

import { shallow } from "enzyme";

import Application from "components/Application";

describe("Application", () => {

    beforeEach(() => {
        Moxios.install();
    });

    describe("#render", () => {

        test("application renders correctly", () => {
            Moxios.stubRequest("https://hostname/token", {
                status: 200,
                responseText: {}
            });

            expect(shallow(<Application />)).toMatchSnapshot();
        });

    });

    afterEach(() => {
        Moxios.uninstall();
    });

});

I should be getting output from the console.log(response); but I don't. I can only get this working if I remove the Moxios.uninstall() line from afterEach. I've also tried other variations like beforeAll / afterAll but to no avail.

For now, since I can't call Moxios.uninstall() on my tests, I've just removed beforeEach / afterEach completely and I'm calling Moxios.install() inside the first describe. But this doesn't fell right.

What might I be doing wrong?

What am I doing wrong?

Wrong example in README

This example seems wrong

    moxios.wait(function () {
      let request = moxios.requests.mostRecent()
      request.reject(errorResp)
      }).catch(function (err) {
        equal(err.status, errorResp.status)
        equal(err.response.message, errorResp.response.message)
        done()
      })
    })

wait() doesn't return Promise so we can't chain catch()

Default moxios import doesn't work in TypeScript

I tried using https://www.npmjs.com/package/@types/moxios in TypeScript:

import moxios from 'moxios';

describe('MoxiosTest', () => {

    beforeEach(() => {console.log(moxios); moxios.install();});
    afterEach(() => moxios.uninstall());

    it('test', () => {
        console.log(moxios);
    });
});

and getting error:

TypeError: Cannot read property 'install' of undefined
	    at Context.<anonymous> (webpack:///src/api/testing1.test.js:5:75 <- src/api/testing1.test.js:1926:53)

I think the problem is how moxios gets exported from moxios.js.

I had to modify:

	exports.default = moxios;
	module.exports = exports['default'];

to

	module.exports = moxios;
	module.exports.default = moxios;

in order to get the default import to work.

This is similar to how axios is exported in axios.js:

module.exports = axios;

// Allow use of default import syntax in TypeScript
module.exports.default = axios;

Wildcard Mock Not Working

Hi,

I have some tests that require wildcards (see example below) but it doesn't look to be working as expected (the requests is not mocked).

moxios.stubRequest('/comments/.*/vote', { status: 200, response: { success: true } })

Any idea why this could be happening?

Thanks in advance

Publish non webpack bundled code

Current moxios is published to npm with a webpack bundled file. This means that you must always pass an axios instance to moxios.install() as webpack rewrites all imports and will never use the axios install from node_modules in a project. It would be nice to see just a babel transform of the code be published to npm.

Usage with Vue and Jest

I have a test as below:

import axios from 'axios';
import moxios from 'moxios';
import Vue from 'vue/dist/vue.js';
...

window.axios = axios;

describe('Component', () => {
    Vue.component('component', Component);
    ...
    ...

    beforeEach(function () {
      // mock axios
      moxios.install(window.axios);
    })

    afterEach(function () {
      // remove mock
      moxios.uninstall(window.axios)
    })

    ...

    it('does something action on click', async() => {
        document.body.innerHTML = `
            <div id="app">
                <component :data="[{id: 1, something: 'else'}]"
                ></component>
            </div>
        `;

        const component = await createVm();

        var button = document.querySelector('.button.is-success');
        button.click();

        await Vue.nextTick(() => {});

        moxios.wait(function () {
            let request = moxios.requests.mostRecent()
            request.respondWith({
                status: 200,
                response: []
            }).then(function () {
                expect(component.data.something).toBe('newness');
                done();
            })
        });
    });
});

async function createVm() {
    const vm = new Vue({
        el: '#app',
    });

    await Vue.nextTick(() => {});

    const component = vm.$children[0];

    return component;
}

The component has a method which is triggered by the button click and has this

axios.post(actionUrl, postData)
    .then( (response) => {
        this.data.something = 'new';
    })
    .catch( (error) => {
        console.log('failed ' + error.status);
    });

I had expected the test to fail, but it doesn't. The component works as desired (checked in a browser). Also doing a console.log() before the axios call also shows up during the test.

However, the axios part is not working. Doing a console.log() doesn't show anything from inside the moxios then() call. It's clear that I am doing something wrong I suppose, just not sure what it is.

Appreciate any insights! 👍

HAR support

I really like moxios and I was wondering if you are planning to support HAR files?

At the moment I am always writing definitions like:

moxios.stubRequest('http://localhost:8080/resource', {
  status: 200,
  responseText: {value: 'Hello'}
});

It would be great if I could load a HTTP Archive which would then define the status and responseText (among other values).

Example:

moxios.stubRequest('./har/response.har');

There is such a functionality provided by sinon-har-server. Maybe you can make use of that!?

support for axios timeouts

As an enhancement, it would be great to support mocking axios timeouts with moxios.

Timeouts are specific to the axios implementation and cannot (currently) be simulated with responses alone.

Here is a PR with a potential enhancement: #8

Mix real requests with mock requests ?

Scenario

During development I am using stubRequest to return mock data for api endpoints that I know are incomplete.

Problem

On urls where there is no stub request to intercept the fetch, the fetch still never goes through - almost like moxios is catching EVERYTHING that goes through axios and not just the urls that match one of the stub requests.

Question

How can I have SOME fetches (which match a stubRequest) return mock data while allowing other fetches (which don't match any stub requests) return real data?

code

        moxios.install();

        const stubs = {};
        //todo: make top three expressions pull from constants @jkr
        stubs["^navigationMock"] = navigationMock;
        stubs["^ancillaryMock"] = ancillaryMock;
        stubs["^pageMock"] = pageMock;
        stubs[constants.EVENT_CALENDAR_HREF] = eventCalendarMock;
        stubs[constants.STYLE_GUIDE_HREF] = styleGuideMock;

        for (const key in stubs) {
            const re = new RegExp(key);
            const mock = stubs[key];
            // console.log(key, re, stubs[key])
            moxios.stubRequest(re, {
                status: 200,
                response: mock
            });
        }
        // console.log(moxios);

        axios.create();

How does one mock axios.all([]) requests?

I'm came across a problem while i was setting up mocking for my project.

I have an axios request that that uses axios.all to make several requests at the same time. Then i thought "how the hell am i going to mock this?".

I'd need to mock about 10 requests to mock the axios.all request, and i don't think that would even work.
Is there functionality to mock an axios.all request?

Update:

I've mocked each request indiviually but is a unefficient and painful process, maybe there's a better way?

stubRequest for specific method?

The only reason why my team hasn't switched from axios-mock-adapter to this is that we can't mock a specific method with moxios. Will this be supported in the future? I can possibly submit a PR but it would be nice with some guidance. Possibly as another argument to stubRequest?

Here's the chunk of code that gives the functionality in axios-mock-adapter: https://github.com/ctimmerm/axios-mock-adapter/blob/811a6a73de6bec643d64fa619fee136a0e3e841f/src/index.js#L86

Moxios Wont Uninstall afterEach / mostRecent() calls last 'it' block

I am writing a test for a post call to my database to create a user, delete a user, and not create user for duplicate email. The issue is that moxios.requests.mostRecent() is calling the very last 'it' block even though it hasn't been called yet.

what am I missing?

Test Code:

describe("\tBackend API Works", ()=>{
      let data, onFulfilled, onRejected, sandbox;
      beforeEach(()=>{
        data = { email: user, password: pw}
        moxios.install()
        onFulfilled = sinon.spy()
        onRejected = sinon.spy()
      })
      afterEach(()=>{
        data = { email: user, password: pw}
        moxios.uninstall()
        onFulfilled = ""
        onRejected = ""
      })
      it("\tCreates Account (API)", function(){
        this.timeout(5000);
        axios.post(ROOT_URL+'/api/signup', data).then(onFulfilled).catch(onRejected)
        moxios.wait(function () {
          let request = moxios.requests.mostRecent();
          request.respondWith({
            status: 200,
            "statusMessage": "Success, User Created!",
            "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiI1ODZhZWU2NTU1ZjE4YzBlYjhmNDNlNDMiLCJpYXQiOjE0ODM0MDI4NTQzMTJ9.9P4Zw-9gC7A2BHGvHWrdx3d1zmV3MGC96APsexl_n4c"
          }).then(()=>{
            expect(onFulfilled.getCall(0).args[0]).to.exist;
            done()
          })
        })
      })
      it("\tDeleted Account (API)", function(){
        data.allow = "true";
        this.timeout(5000);
        axios.post(ROOT_URL+'/api/a666Route', data).then(onFulfilled).catch(onRejected)
        moxios.wait(function () {
          let request = moxios.requests.mostRecent();
          request.respondWith({
            status: 200,
            "statusMessage": "Deleted User"
          }).then(()=>{
            expect(onFulfilled.getCall(0).args[0]).to.exist;
            done()
          })
        })
      })
      it("\tWont Let You Signup w/ a Duplicate Username", function(done) {
        this.timeout(5000);
        axios.post(ROOT_URL+'/api/signup', {"email": "Dan", "password": "Dan"}).then(onFulfilled).catch(onRejected)
        moxios.wait(function () {
          let request = moxios.requests.mostRecent()
          request.respondWith({
            status: 422,
            "statusMessage": "Email is in use."
          }).then(()=>{
            expect(onRejected.getCall(0)).to.exist;
            done()
          })
        })
      })
    })

Moxios (0.4.0) not working with Axios 0.19.1

Moxios last version (0.4.0) just stopped working with Axios 0.19.1 - released 2 days ago.

I just changed back Axios version in my project (0.19.0) and it's working fine.

Any idea why?

stubOnce behavior / documentation

The docs for stubOnce state: "Stub a response to be used one or more times to respond to a request matching a method and a URL or RegExp.".

From the method name I was expected a different behavior, namely that the response would only used once and subsequent requests would fail.

Feature: Method getLast for moxios.requests

Hello there.

It will be cool to add method getLast, that takes reverse array of moxios.requests and returns last of found.

It is valuable as mostRecent method in cases with splitting multiple logic inside moxios.wait method.

Example:

moxios.wait(() => {
  moxios
    .requests
    .getLast('post', '/foo')
    .respondWith(fooResponse)
    .then(doSomething)

  moxios
    .requests
    .getLast('post', '/bar')
    .respondWith(barResponse)
    .then(doSomething)
})

Test passed even though it shouldn't be ?

Hi, I added an unit testing using moxios for our React application.
It seems that my test with moxios passes even though the test is a false condition.

Here is the code.

login-test.js

` . import React from 'react';
import Login from '../../src/components/Login';
import axios from 'axios';
import moxios from 'moxios';
describe('Login test', function () {
let data;

beforeEach(function () {
    data = { email: 'sample', password: 'sample' }
    moxios.install();
});

afterEach(function () {
    data = { email: 'sample', password: 'sample' }
    moxios.uninstall();
});

it('Send Login data', function (done) {

    axios.post('/login');

    moxios.wait(function () {
        const request = moxios.requests.mostRecent();
        request.respondWith({
            status: 200,
            response: { message: 'successfull', status: '200' },
        }).then(function () {
            equal(login.called, true)
        })
    });

    done()
  })
 })` 

// test passed

Here is the code with a false condition. I didn't assign a post router.

` . import React from 'react';
import Login from '../../src/components/Login';
import axios from 'axios';
import moxios from 'moxios';
describe('Login test', function () {

  let data; 

beforeEach(function () {
    data = { email: 'sample', password: 'sample' }
    moxios.install();
});

afterEach(function () {
    data = { email: 'sample', password: 'sample' }
    moxios.uninstall();
});

it('Send Login data', function (done) {

    **axios.post('/');**

    moxios.wait(function () {
        const request = moxios.requests.mostRecent();
        request.respondWith({
            status: 200,
            response: { message: 'successfull', status: '200' },
        }).then(function () {
            equal(login.called, true)
        })
    });

    done()
})
})`

This test passed. I tried testings with several conditions and the tests passed in most cases.

request.reject undefined (using typescript)

Following the example below from the README.de file, I'm getting request.reject equal to undefined. The only way that I was able to mock an error on the request was by using respondWith passing status 4xx. Am I doing something wrong?

moxios.wait(function () {
  let request = moxios.requests.mostRecent()
  request.reject(errorResp)
  }).catch(function (err) {
    equal(err.status, errorResp.status)
    equal(err.response.message, errorResp.response.message)
    done()
  })
})

why catch method is not invoked?

test('should fails with incorrect secret_key', (done) => {

        const errorResp = {
            status: 422,
            response: mock_objects.auth_inv_secret
        };
        conf.secret_key = 'aaabbb';
        let api = new ApiRequest(conf);
        api.Auth(); //call to backend 

        moxios.wait(function () {
            let request = moxios.requests.mostRecent();
            request.reject(errorResp);
        }).catch(error => {
            console.log(error);
            done();
        });
    });

Testing with jest i get -> TypeError: Cannot read property 'catch' of undefined

Tracker.get() method tests RegExp against itself rather then testing url with it

When get() method is called with url it might return wrong result due to bug in RegExp testing.
Snippet to reproduce:

it('should find single stub by url using RegExp', function () {
        moxios.stubOnce('GET', /^\/users\/\d+$/ , {
          status: 200
        })

        let request = moxios.stubs.get('GET', '/users/12345')

        notEqual(request, undefined)
})

Problems with Jest

I'm trying to run an example using Jest that's nearly identical to the first example in the docs, and I'm getting the following error after I try to run expect(A).toEqual(B):

(0 , _jest2.default) is not a function

Make wait only resolve currently queued requests

The setTimeout implementation of wait() causes requests that get queued as a result of a prior axios requests to ALSO be fulfilled.

Consider the following script which gets executed.

axios.get('https://www.google.com').then(() => {
   axios.get('https://www.yahoo.com')
})

Our test file looks like so:

it('calls appropriate requests', function(done){
  moxios.wait(() => {
    expect(moxios.requests.mostRecent().config.url).to.equal('https://www.google.com')
    moxios.wait(() => {
       expect(moxios.requests.mostRecent().config.url).to.equal('https://www.yahoo.com')
       done()
    })
  })
})

But this doesn't work, since yahoo.com becomes the last request after the first wait().

We probably need two methods, one for resolving already queued requests at the time wait() is invoked, and one for waiting until all moxios requests (including ones triggered in moxios promise handlers) are finished - maybe named moxios.waitAll()?

I'm no guru of testing frameworks, but this behavior seems desirable and typical since it gives developers much more control over what requests actually get initiated, and lets them inspect the application state at every step of the process rather than only at the very end.

Make wait() compatible with global setTimeout stub

Many stubbing libraries (SinonJS in particular) provide a handy way to stub out built in date and timers. In Sinon this is sinon.useFakeTimers(). However, since the wait() function internally uses setTimeout, you have to manually increment the clock in order to get the wait() callback to fire, which is annoying.

Flaky Tests with Moxios

I'm using moxios in two files to mock out API requests and getting tests that seem to randomly fail.
For example:

import { expect } from 'chai'
import moxios from 'moxios'
import { SharedState, updateRenewal, mbcRequest, fetchVersions } from '../../../app/javascript/packs/sharedState.js'

const genericResponse = {
  id: 1,
  status: 'approved',
  versions: ['underwriting', 'approved']
}

describe('SharedState', () => {
  SharedState.currentRenewal = { id: 1 }

  beforeAll(() => {
    moxios.install()
    moxios.stubRequest('/commercial_renewals/1', {
      status: 200,
      response: genericResponse
    })
  })

  afterAll(() => {
    moxios.uninstall()
  })

  describe('updateRenewal', () => {
    let basic_params = {
      id: 1,
      status: 'approved'
    }

    it('updates the attributes on the SharedState updatedRenewals field', (done) => {
      let attribute = basic_params['status'];

      moxios.wait(() => {
        updateRenewal(basic_params);
        expect(SharedState.updatedRenewals[basic_params['id']]['status']).to.equal(attribute);
        done();
      })
    });
  });
...

If I run this test file, followed by another test file with a similar moxios setup, I get various errors around afterAll and variables being undefined and I don't quite get why.

moxios.requests.mostRecent() is returning undefined

I am using Webpack in React (16.12)and after running test getting below error
I am testing with Jest and enzyme

Error: Uncaught [TypeError: Cannot read property 'respondWith' of undefined]
at reportException (/Users/saurabh/Desktop/project/rewards-app-fe/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:66:24)
at Timeout.callback [as _onTimeout] (/Users/saurabh/Desktop/project/rewards-app-fe/node_modules/jsdom/lib/jsdom/browser/Window.js:680:7)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7) TypeError: Cannot read property 'respondWith' of undefined
at /Users/saurabh/Desktop/project/rewards-app-fe/src/Store/Actions/AuthActions/AuthActions.test.js:35:15
at Timeout.callback [as _onTimeout] (/Users/saurabh/Desktop/project/rewards-app-fe/node_modules/jsdom/lib/jsdom/browser/Window.js:678:19)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)

Testing axios interceptors

Hello,

I would like to test axios interceptors.
Is there a way to do this with moxios?

I currently have this interceptor:

axios.interceptors.response.use(null, (error) => {
  if (error.response.status === 401) {
    window.location.assign(`${error.response.data.loginUrl}/?redirect=${encodeURIComponent(window.location.href)}`);
  }
  return Promise.reject(error);
});

And have a test like so:

test('should redirect if 401', (done) => {
  window.location.assign = jest.fn();

  moxios.withMock(function () {
    axios.get('/foo');

    moxios.wait(async () => {
      const request = moxios.requests.mostRecent();
      await request.respondWith({
        status: 401,
        response: {
          data: {
            loginUrl: 'hello.world'
          }
        }
      });
      expect(window.location.assign).toHaveBeenCalled();
      done();
    });
  });
});

This throws me: Error: Request failed with status code 401.
And any console.log in the interceptor isn't displayed.

Any idea how I could proceed?

Thank you!

stubRequest inside withMock doesn't work

Seems stubRequest doesn't work inside withMock.
If I use moxios.install()/uninstall() in beforeEach/afterEach stubRequest() works good.
If I use just withMock() without stubRequest and then

moxios.wait(... 
moxios.requests.mostRecent().respondWith(...).then(...)
...

it works good too.
But if I use it this way

describe('Test suite', function () {
  it('#1', function (done) {
    moxios.withMock(function () {
      moxios.stubRequest('/say/hello', {
        status: 200,
        responseText: 'hello'
      })

      let onFulfilled = jasmine.createSpy('spy1')
      axios.get('/say/hello').then(onFulfilled)

      moxios.wait(function () {
          expect(onFulfilled.calls.mostRecent().args[0].data).toBe('hello')
          done()
      })
    })
  })
})

it doesn't work.

Possible to respond differently based on order of calls?

Trying to test retry logic of a method, so I've it wired up like this:

    moxios.wait(() => {
      const request = moxios.requests.at(0)
      request.respondWith({
        status: 401
        , response: mockApiError
      })

      const nextRequest = moxios.requests.at(1)
      nextRequest.respondWith({
        status: 200
        , response: mockApiResponse
      })
    })

    const mockRequest = {
      headers: {}
      , method: 'get'
      , url: 'to/no/where'
    }

    const response = await tryMakeRequest(mockRequest)

    expect(response.status).toBe(200)
    expect(response.data).toEqual(mockApiResponse)

The test fails with this error:

    Timeout - Async callback was not invoked within timeout specified by
jasmine.DEFAULT_TIMEOUT_INTERVAL.

      at node_modules/jest-jasmine2/build/queue_runner.js:64:21
      at Timeout.callback [as _onTimeout] (node_modules/jsdom/lib/jsdom/browser/Window.js:523:19)
      at ontimeout (timers.js:469:11)
      at tryOnTimeout (timers.js:304:5)
      at Timer.listOnTimeout (timers.js:264:5)

Any ideas what am I missing here?

test axios in a Vue project

There are some code,

    let msg 
    it ('should send off a request when clicked', (done) => {
        moxios.stubRequest( URL, {
            status: 200,
            response: []
        })

       axios.get(URL).then(res => {
          console.log(res)
          msg = res
       })

        moxios.wait(() => {
            expect(msg.status).toEqual(200)
            done()
        })
    })

When I test it, I found out,two URL as long as it is the same, the test will be successful.
It does not get the interface from the server side.
What I want to know is how to get the interface through the server?

Feature request:

Hi, I'm using Moxios to build a live demo of SPA project and while was able to do so, its not really strightforward.

I would like to request a function similar to stubRequest with a callback.

moxios.stubRequest('/say/hello', request => {
  const data = {} // do your thing
  return {
    status: 200,
    data
  }
})

Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.

I have a test with moxios and those results are an error, I read the docs and I wrote the same form that of these describe in how define an async test,the error is, I read also the docs of jasmine. Do you knows what happens?

Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
at node_modules/jest-jasmine2/build/queue_runner.js:65:21
at Timeout.callback [as _onTimeout] (node_modules/jsdom/lib/jsdom/browser/Window.js:523:19)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
Test

`import configureStore from 'redux-mock-store';
import thunk from 'redux-thunk';
import multi from 'redux-multi';
import promise from 'redux-promise';

import moxios from 'moxios';

import LocalStorageMock from '../../layouts/mock-localstorage'
import { password, leavePassword, restorePass, types } from '../../actions/password-actions';

//const middlewares = [multi];
const middlewares = [multi,thunk];
//const middlewares = [multi,promise];
const mockStore=configureStore(middlewares);

const baseUrl = 'localhost/project';
const REGISTER_ENDPOINT = 'account/password';
const RESTORE_ENDPOINT = 'account/reset_password/init';

let originalTimeout;
beforeEach(() =>{
//originalTimeout = jasmine.DEFAULT_TIMEOUT_INTERVAL;//that not works
//jasmine.DEFAULT_TIMEOUT_INTERVAL = 5000;//that not works
moxios.install();
});
afterEach(() => {
localStorage.clear();
moxios.uninstall();
//jasmine.DEFAULT_TIMEOUT_INTERVAL = originalTimeout;//that not works
});

global.localStorage= new LocalStorageMock('auth');

it('when user set password isnt valid', async(done)=>{ //it('when user set password isnt valid',()=>{
const store = mockStore({password:{}});
const path = baseUrl + REGISTER_ENDPOINT;
moxios.stubRequest(path,{
status: 404,
response:{
message:'BAD_REQUEST'
}
});

const values = { 
    newPassword: 'password',
    email: '[email protected]',
    key: 'eXyGsaerFAS213das&%ASDas'
};


store.dispatch(password(values));
const actions= store.getActions();


expect(actions.length).toBe(2);
expect(actions[0].type).toBe(types.SETPASS_STARTED);
expect(actions[1].type).toBe(types.SETED_PASS);
expect(actions[1].payload).not.toBe(null || undefined);

await actions[1].payload.then((response)=>{
expect(actions[1].payload.response.status).toEqual(404);
expect(actions[1].payload.message).toEqual('BAD_REQUEST');
done();
});

});Action creator// tipos de acciones que se generaran
export const types = {
SETPASS_STARTED: '#password/setPass_started',
SETED_PASS: '#password/seted_pass',
LEAVE_COMPONENT: '#password/leave_pass',
RESTORE_STARTED: '#password/restore_started',
RESTORE_PASS: '#password/restore',
};

// creador de accion cuando se setea el password por primera vez
export const password = (values) => {
const data = {
newPassword: values.password,
email: values.email,
key: values.key,
};
let request = axios.post(${Config.baseUrl}${REGISTER_ENDPOINT}, data, {
auth: {
username: Config.oauth.appUser,
password: Config.oauth.appPassword,
},
});

return [{
type: types.SETPASS_STARTED,
}, {
type: types.SETED_PASS,
payload: request,
}];
};`

mocking axios in extended classes

So, im using a heavily extended vue-mc,

and i am trying to ensure that the responses get handled correctly to my own project specifications,

how ever, it seems that despite the fact that vue-mc uses axios. the import for this is not being mocked, as it still has the httpAdpater, instead of the mock adapter.

Vue-mc uses a Request class with a single method to use axios, so i am unsure how to get around this.

Documentation of Examples

Hello!

I found the following example syntax not as intuitive as it could be:

      // Alternatively URL can be a RegExp
      moxios.stubRequest(/say.*/, {/* ... */})

Could I recommend the following?

      // Alternatively URL can be a RegExp, useful when testing URLs with parameters
      moxios.stubRequest( new RegExp("/say/.*"), {/*...*/})

moxios.requests.mostRecent() returns undefined

I use karma, jasmine and phantomJS with babel-polyfill. mostRecent always returns undefined even if I call axios in the test directly.

For example:

axios = require 'axios'
moxios = require 'moxios'

describe 'Test moxios', () ->
  beforeEach () ->
    moxios.install()

  afterEach () ->
    moxios.uninstall()

  it 'mostRecent should return a request', () ->
    axios('http://example.com').then (result) -> console.log result
    moxios.wait () ->
      console.log moxios.requests.mostRecent()
      # undefined

how to use moxios to return streams that have images

I am trying to use moxios to mock the following scenario.

axios.default.get(imageUrl, { responseType: 'stream' })

To unit test the above, I am trying to write jest with the following.

    moxios.stubRequest('http://abc.com/text.jpg', {
        status: 200,
        response: { data: fs.createReadStream(`${__dirname}/text.png`) }
    });

But the response.data. When I use response.data.pipe(somewriteablestream) it does not work.

Any help appreciated for mocking a get request returning a stream object.

Is there any plan to release the next version?

Hey,
I'm using this mock library and I see that the needed changes for my case in this merged PR -> #35

Can I get some estimation on when this change will be landed? (Last release was 3 years ago on npm)

Without this PR you can't mock multiple requests with the same URL if the method is the only difference between them.

Thanks

problem with custom instances

I have following file with a custom axios instance:

import axios from 'axios';
import {AxiosInstance} from 'axios';
import { Loading } from 'quasar';

let axiosInstance = axios.create({
  baseURL: 'http://localhost:8080/api/'
});

axiosInstance.interceptors.request.use(function (config) {
  Loading.show();
  return config;
});

axiosInstance.interceptors.response.use(function (response) {
  Loading.hide();
  return response;
}, function (error) {
  Loading.hide();
  return Promise.reject(error);
});


export default axiosInstance;

I consume this file in processing and in a test, but it doesn't work.
When I use the default instance, everything works as expected:

Inside a VueJs model is do:

import axiosInstance from '../../configs/axiosInstance';
...
axiosInstance.get(todos). then ....

And in the test I use moxios as follows:

import axiosInstance from '../../configs/axiosInstance';
moxios.install(axiosInstance);

moxios.stubRequest('todos', {
    status: 200,
    response:
       [
         {
          'userId': 1,
          'id': 1,
          'title': 'delectus aut autem',
          'completed': false
        },
        {
          'userId': 1,
          'id': 2,
          'title': 'quis ut nam facilis et officia qui',
          'completed': false
        }
      ]
    }
  )

  const vm = new CardTodoComponent();


 vm.$mount();
 expect(vm.todos.length).equal(2);
 done();

As I said, when I switch both in the test and the processing to the default axios instance, the fails succeeds and get the amount of records.

What am I doing wrong?

moxios.install() does not seem to install adapter

Hi,

I'm trying to use moxios, but I find that the requests are performed as usual and moxios.requests.mostRecent() returns undefined.

It seems that moxios does not install any mock adapter.

Here's a minimal test:

import moxios from "moxios";
import axios from "axios";

describe("moxios", () => {
  it("mocks axios", () => {
    console.log("Adapter before: ");
    console.log(axios.defaults.adapter);
    moxios.install();
    console.log("Adapter after installing: ");
    console.log(axios.defaults.adapter);
    moxios.uninstall();
    console.log("Adapter after uninstalling: ");
    console.log(axios.defaults.adapter);
  });
});

Output:

Adapter before: 
[Function: httpAdapter]
Adapter after installing: 
[Function: httpAdapter]
Adapter after uninstalling: 
[Function: httpAdapter]

I run the test with this command:

node_modules/.bin/mocha --compilers js:babel-core/register moxios.js

can moxios catch request from click event?

when i use redux, and i click a button, call a action, in action, a instance of axios was called, code like this

beforeEach(() => {
    moxios.install(instance);
    store = configureStore(initialStore)
    wrapper = Enzyme.mount(
        <Provider store={store}>
            <AppInput onChange={updateAppInfo}/>
        </Provider>
    )
})
it('updateAppInfo', (done) => {
        moxios.stubRequest('/app/get', {
            status: 200,
            responseText: 'hello'
        })
        wrapper.find('.xj-appinput-item').at(0).simulate('click');
        
        moxios.wait(() => {
            let request = moxios.requests.mostRecent();
            request.respondWith({
                status: 200,
                response: { a: 22 }
            }).then(() => {
            });
        });
    })

updateAppInfo function send a request which url is /app/get,
and as expect, moxios will catch this request,
but i got this error,
TypeError: Cannot read property 'respondWith' of undefined
so i wonder how to fix this?

Tracking what Requests are called with

I'd like to mimic something like what jest#wasCalledWith does so I can verify that a call was requested with the correct data. Is that currently possible? The only insight we have into that at the moment is that a URL may have been updated if it contained params that were interpolated

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.