Reece Daniels

@josep11 have you run into this problem since?

Thanks i'll close it

Hi @lonecrane, Yes that parameter is designed to just be the name of the profile to be used. When I added this functionality the package was only designed to be...

If you're looking to work on changes locally to chrome-cookies-secure there are two ways. 1) You can test changes quickly by modifying the code of `chrome-cookies-secure` directly within `node_modules` of...

I think this functionality was only added recently. Are you running the latest version of chrome-cookies-secure? See https://github.com/bertrandom/chrome-cookies-secure/pull/19 It may be worth dropping a comment in that PR or tagging...

Hi @oliver-gomes, I'm afraid I can't help out with Windows issues as I'm Mac only. I'd suggest looking at PR #19 , specifically the new `if` blocks added. Perhaps try...

I'm afraid I don't have any way of testing this on Linux

Thanks for your comment. I'd be up for re-upping to npm as another package providing the license is set correctly. Might be able to look into this week.

@suntong are you still using the fork at https://github.com/paragbaxi/chrome-cookies-secure? I'm stumped why that fork would work and this package wouldn't as the runtime diff changes don't seem to touch anything...

@suntong that just looks like the promise wrapper and readme update which is something that is available in this repo (in fact was added here by myself originally). ~Are you...