We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System: Windows 10 Node.js version: v14.18.1 Chrome version: 96.0.4664.55
When I use custom userDataDir, and remove it after chrome exit.
const customUserDataDir = 'D:\\.browser-temp\\chrome-4f32efbed74f445c'; const chrome = await launch({ userDataDir: customUserDataDir }); chrome.process.on('close', () => { if (fs.existsSync(customUserDataDir)) { const rm = fs.rmSync || fs.rmdirSync; rm(customUserDataDir) } });
(node:3204) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, unlink 'D:\\.browser-temp\\chrome-4f32efbed74f445c\\chrome-err.log'
The outFile and errFile should be handled by fs.closeSync when chrome exit.
The text was updated successfully, but these errors were encountered:
#259 Please review it.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Environment Information
System: Windows 10
Node.js version: v14.18.1
Chrome version: 96.0.4664.55
Provide the steps to reproduce
When I use custom userDataDir, and remove it after chrome exit.
What is the current behavior?
What is the expected behavior?
The text was updated successfully, but these errors were encountered: