Use latest version (v1.0.1) of chrome-cookie-path which supports windows also

add delete before insert flag for insert cookie

lodash is in package lock but not in package.json. It must be either mentioned in the manifest, or to be rewritten without using _.get.

Move all constants like this
https://github.com/arshadkazmi42/chrome-cookie/blob/master/index.js#L8
in a constant file

if a key is missing from the request data, add handler to support that or give proper messaging.
Example:

const ChromeCookie = require('chrome-cookie');
const CCookie = new ChromeCookie();



const DATA = [
      {
        'creation_utc': 'now',
        'encrypted_value': 'enc2',
        'expires_utc': 'never',
        'has_expires': 'yes',
        'host_key': 'youtube.com',
        'is_httponly': 'yes',
        'is_persistent': 'no',
        'is_secure': 'yes',
        'last_access_utc': 'now',
        'name': 'youtube',
        'path': '/root',
        'priority': 'no',
        'value': 'kazmi',
        'samesite': -1,
        'encrypted_value': {}
      }
    ];

CCookie.setCookie(DATA);

above code breaks if we remove encrypted_value

1. Install npm badger npm install npm-badger -g
2. Clone this repository git clone https://github.com/arshadkazmi42/chrome-cookie
3. Go to root directory cd chrome-cookie
4. Run npm badger npm-badger
5. Commit README.md file
6. Create Pull Request

add api for deleting cookie

Use chrome cookie path to get cookies db path based on OS

Seems chrome has introduced some more columns in its cookies table.

Revisit the and update the model

One column we know about its top_frame_site_key

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request