npm package: @kazuma0129/chrome-cookies-secure
Description: Extract encrypted Google Chrome cookies for a url on a Mac or Linux
Author: Kazuma Ohashi
Latest version: 0.0.4

# chrome-cookies-secure-ts

Extract encrypted Google Chrome cookies for a url on Mac OS X, or Linux

## Installation

```
npm install @kazuma0129/chrome-cookies-secure
```

## API

## getCookies(url[,format],callback,profile)

`url` should be a fully qualified url, e.g. `https://www.example.com/path`

`format` is optional and can be one of the following values:

| format     | description                                                                                                                                                                            |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| curl       | [Netscape HTTP Cookie File](http://curl.haxx.se/docs/http-cookies.html) contents usable by curl and wget                                                                               |
| jar        | cookie jar compatible with [request](https://www.npmjs.org/package/request)                                                                                                            |
| set-cookie | Array of Set-Cookie header values                                                                                                                                                      |
| header     | `cookie` header string, similar to what a browser would send                                                                                                                           |
| puppeteer  | an array of objects that can be loaded into puppeteer using the `setCookie(...)` method                                                                                                |
| object     | (default) Object where key is the cookie name and value is the cookie value. These are written in order so it's possible that duplicate cookie names will be overriden by later values |

If `format` is not specified, `object` will be used as the format by default.

Cookie order tries to follow [RFC 6265 - Section 5.4, step 2](http://tools.ietf.org/html/rfc6265#section-5.4) as best as possible.

## Examples

## basic usage

```javascript
const chrome = require("chrome-cookies-secure");
chrome.getCookies("https://www.example.com/path/", function (err, cookies) {
  console.log(cookies);
});
```

## jar used with request

```javascript
const request = require("request");
const chrome = require("chrome-cookies-secure");

chrome.getCookies("https://www.example.com/", "jar", function (err, jar) {
  request(
    { url: "https://www.example.com/", jar: jar },
    function (err, response, body) {
      console.log(body);
    }
  );
});
```

## puppeteer with specific Chrome profile

```javascript
const chrome = require("chrome-cookies-secure");
const puppeteer = require("puppeteer");

const url = "https://www.yourUrl.com/";

const getCookies = (callback) => {
  chrome.getCookies(
    url,
    "puppeteer",
    function (err, cookies) {
      if (err) {
        console.log(err, "error");
        return;
      }
      console.log(cookies, "cookies");
      callback(cookies);
    },
    "yourProfile"
  ); // e.g. 'Profile 2'
};

getCookies(async (cookies) => {
  const browser = await puppeteer.launch({
    headless: false,
  });
  const page = await browser.newPage();

  await page.setCookie(...cookies);
  await page.goto(url);
  await page.waitFor(1000);
  browser.close();
});
```

## Calling using async/await

```javascript
const chrome = require("chrome-cookies-secure");
const url = "https://www.yourUrl.com/";

const myFunction = async () => {
  const cookies = await chrome.getCookiesPromised(
    url,
    "puppeteer",
    "Profile 28"
  );
  // ..... Use the cookies
};
```

## Limitations

On OS X, this module requires Keychain Access to read the Google Chrome encryption key. The first time you use it, it will popup this dialog:

![image](https://raw.githubusercontent.com/bertrandom/chrome-cookies-secure/gh-pages/access.png)

The SQLite database that Google Chrome stores its cookies is only persisted to every 30 seconds or so, so this can explain while you'll see a delay between which cookies your browser has access to and this module.

## License

This software is free to use under the MIT license. See the [LICENSE file][] for license text and copyright information.

[license file]: https://github.com/bertrandom/chrome-cookies-secure/blob/master/LICENSE.md