Skip to main content
Version: Next

BrowserLaunchError

Errors of CriticalError type will shut down the whole crawler. Error handlers catching CriticalError should avoid logging it, as it will be logged by Node.js itself at the end

Hierarchy

Index

Constructors

publicconstructor

  • new BrowserLaunchError(...args: [message?: string, options?: ErrorOptions]): BrowserLaunchError
  • Parameters

    • rest...args: [message?: string, options?: ErrorOptions]

    Returns BrowserLaunchError

Properties

externaloptionalinheritedcause

cause?: unknown

externalinheritedmessage

message: string

externalinheritedname

name: string

externaloptionalinheritedstack

stack?: string

staticexternaloptionalinheritedprepareStackTrace

prepareStackTrace?: (err: Error, stackTraces: CallSite[]) => any

Optional override for formatting stack traces

@see

Type declaration

    • (err: Error, stackTraces: CallSite[]): any
    • Parameters

      • externalerr: Error
      • externalstackTraces: CallSite[]

      Returns any

staticexternalinheritedstackTraceLimit

stackTraceLimit: number

Methods

staticexternalinheritedcaptureStackTrace

  • captureStackTrace(targetObject: object, constructorOpt?: Function): void
  • Create .stack property on a target object


    Parameters

    • externaltargetObject: object
    • externaloptionalconstructorOpt: Function

    Returns void