How to pass userDataDir profile folder to Puppeteer The first time you run the above code, you will have to comment out the fs.readFile to fs.writeFile as the UserDirDirectory is created if it does not exist the first time that Chrome is started.Īll profile related data is then stored in the customChrome/Default folder. Essentially, Puppeteer creates a custom profile each time it runs, we can override that profile and define the download directory. This will set the default download directory for files before the process starts. _directory = path.resolve(_dirname, './downloads') įs.writeFileSync(customChrome+'/Default/Preferences', JSON.stringify(obj)) Īrgs:
_directory = path.resolve(_dirname, './downloads') Let prefs = fs.readFileSync(customChrome+'/Default/Preferences') I was able to set the download location using the following code, let customChrome = path.resolve(_dirname, './customChrome') To wait for all downloads to complete with Puppeteer using request interception, you can use the request event to intercept all network requests made by the browser and track when they are finished.I realize this is an old thread, but this thread popped up first for me when looking for how to set Puppeteer default download location. Finally, we close the browser instance.īy using the download event, we can wait for all downloads to complete with Puppeteer in a reliable and efficient way. We then navigate to the page that initiates the download and wait for all downloads to complete using the waitForDownload method. We add a listener to the download event to log when a download is completed. We then set the download behavior for the page to allow downloads and specify the download path. In this code, we first create a new browser instance using Puppeteer and a new page.
send ( 'tDownloadBehavior', ) await page. Const puppeteer = require ( 'puppeteer' ) const browser = await puppeteer.
0 kommentar(er)
