Package Exports
- axios-cookiejar-support
- axios-cookiejar-support/noop.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (axios-cookiejar-support) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
axios-cookiejar-support
Add tough-cookie
support to axios
.
Install
$ npm i axios @3846masa/axios-cookiejar-support
-- OR --
$ npm i axios axios-cookiejar-support # Same as above
Note | If you don't mind to use a scoped library, please use the scoped library. To put my account name in your dependencies is my pleasure :)
Usage
const axios = require('axios').default;
const axiosCookieJarSupport = require('@3846masa/axios-cookiejar-support').default;
// const axiosCookieJarSupport = require('axios-cookiejar-support').default;
const tough = require('tough-cookie');
axiosCookieJarSupport(axios);
const cookieJar = new tough.CookieJar();
axios.get('https://google.com', {
jar: cookieJar, // tough.CookieJar or boolean
withCredentials: true // If true, send cookie stored in jar
})
.then(() => {
console.log(cookieJar);
});
See examples.
Extended Request Config
c.f.) https://github.com/mzabriskie/axios#request-config
{
// `jar` is tough.CookieJar instance or boolean.
// If true, axios create CookieJar automatically.
jar: undefined, // default
// **IMPORTANT**
// If false, axios DONOT send cookies from cookiejar.
withCredentials: false // default
}
Browser
Running on browser, this library becomes noop (config.jar
might be ignored).
Contribution
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request