Open nvanderperren opened 3 years ago
I think this is a just a typo in the mac version of the browser finding code, here is https://github.com/N0taN3rd/Squidwarc/blob/63026b6f4c30b83541f23fc7531126bc7e8747af/lib/launcher/chromeFinder.js#L275
let sortedExes = installations
// assign priorities
.map(inst => {
for (const pair of priorities) {
if (pair.regex.test(inst)) {
return { path: inst, weight: pair.weight }
}
}
return { path: inst, weight: defaultPriority }
})
// sort based on priorities
.sort((a, b) => b.weight - a.weight)
// remove priority flag
.map(pair => pair.path)[0] # <=== this [0] is only in the mac version of this function
if (sortedExes.length > 0) {
return sortedExes[0]
}
Will try to get access to a mac to test changing it to .map(pair => pair.path)
Are you submitting a bug report or a feature request?
Bug report
What is the current behavior?
I get an error when I want to start a crawl. This is the error
This is my configuration file:
Because it says that mode is undefined, I also placed
mode
undercrawlControl
as suggested in issue #50, but that doesn't solve the issueWhat is the expected behavior?
A starting crawl.
What's your environment?
node v14.12.0 Squidwarc: current master macOS High Sierra 10.13.6 Chrome Versie 86.0.4240.80 (Officiële build) (x86_64)
Other information
I don't have this issue if I use puppeteer.