Skip to main content
Version: 3.11

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

Properties

Methods

Constructors

publicconstructor

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

  • Parameters

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

    Returns BrowserLaunchError

Properties

externaloptionalcause

cause?: unknown

externalmessage

message: string

externalname

name: string

externaloptionalstack

stack?: string

staticexternaloptionalprepareStackTrace

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

Optional override for formatting stack traces

@see

https://v8.dev/docs/stack-trace-api#customizing-stack-traces

Type declaration

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

    • Parameters

      • externalerr: Error
      • externalstackTraces: CallSite[]

      Returns any

staticexternalstackTraceLimit

stackTraceLimit: number

Methods

staticexternalcaptureStackTrace

  • captureStackTrace(targetObject: object, constructorOpt?: Function): void

  • Create .stack property on a target object

    Parameters

    • externaltargetObject: object
    • externaloptionalconstructorOpt: Function

    Returns void

Page Options