Setup `user-data-dir` flag about chrome-aws-lambda HOT 2 CLOSED

@Kikobeats As @TimotheeJeannin mentioned, puppeteer already sets a user-data-dir by default:

const CHROME_PROFILE_PATH = path.join(os.tmpdir(), 'puppeteer_dev_profile-');

from chrome-aws-lambda.

Puppeteer already creates a temporary user data dir. See Launcher.js line 113.

I think it's good to provide a default set of arguments that make the chromium binary work well with AWS Lambda but setting a default user data directory is too much. Some people might want to have only one data dir reused across invocations some other might want to have a new one for each invocation. I don't think this package should be responsible for this.

from chrome-aws-lambda.