Focused crawls are collections of frequently-updated webcrawl data from narrow (as opposed to broad or wide) web crawls, often focused on a single domain or subdomain.
Similar to #186 but rather than silence the logs, we might want to elaborate on them. That issue specifically mentions "for example, if the agent server isn't running" which is the most likely reason for that error. We should state so in the error message.
Current:
`[percy] Error fetching DOM library, disabling: ${err}`
Sometimes the percy snapshots are missing placeholders/text for our components. We are using next.js to spin up our servers and using emotion for the styled components.
Obviously I can read the source (and I'm about to, right after this), but it seems like a very core piece of this library is the loader, and it would be useful to have an overview of what's available, what the options are and how they work.
Thanks! Looking forward to getting snapshots working.
It would be nice to suppress Percy log output entirely. In theory, this shouldn't be too hard. We would probably want to add a new config option (flag, .percy.yml, & an env var) to disable logging. Seems like we'll just need to pass silent: true to the logger(s) when that config option is present.
cc: @wwilsman since you recently upgraded us to winston 3.
Similar to #186 but rather than silence the logs, we might want to elaborate on them. That issue specifically mentions "for example, if the agent server isn't running" which is the most likely reason for that error. We should state so in the error message.
Current:
`[percy] Error fetching DOM library, disabling: ${err}`Possible suggestion?:
// We know the dom librar