AppPageRenderResultMetadata: {
    cacheControl?: CacheControl;
    fetchMetrics?: FetchMetrics;
    fetchTags?: string;
    flightData?: Buffer;
    headers?: OutgoingHttpHeaders;
    postponed?: string;
    renderResumeDataCache?: RenderResumeDataCache;
    segmentData?: Map<string, Buffer>;
    staticBailoutInfo?: {
        description?: string;
        stack?: string;
    };
    statusCode?: number;
}

Type declaration

  • Optional cacheControl?: CacheControl
  • Optional fetchMetrics?: FetchMetrics
  • Optional fetchTags?: string
  • Optional flightData?: Buffer
  • Optional headers?: OutgoingHttpHeaders

    The headers to set on the response that were added by the render.

  • Optional postponed?: string

    The postponed state if the render had postponed and needs to be resumed.

  • Optional renderResumeDataCache?: RenderResumeDataCache

    In development, the resume data cache is warmed up before the render. This is attached to the metadata so that it can be used during the render. When prerendering, the filled resume data cache is also attached to the metadata so that it can be used when prerendering matching fallback shells.

  • Optional segmentData?: Map<string, Buffer>
  • Optional staticBailoutInfo?: {
        description?: string;
        stack?: string;
    }
    • Optional description?: string
    • Optional stack?: string
  • Optional statusCode?: number