Back to Qwik

@builder.io/qwik-city/vite/cloudflare-pages API Reference

packages/docs/src/routes/api/qwik-city-vite-cloudflare-pages/index.mdx

1.7.11.7 KB
Original Source

API › @builder.io/qwik-city/vite/cloudflare-pages

<h2 id="cloudflarepagesadapter">cloudflarePagesAdapter</h2>
typescript
export declare function cloudflarePagesAdapter(
  opts?: CloudflarePagesAdapterOptions,
): any;
<table><thead><tr><th>

Parameter

</th><th>

Type

</th><th>

Description

</th></tr></thead> <tbody><tr><td>

opts

</td><td>

CloudflarePagesAdapterOptions

</td><td>

(Optional)

</td></tr> </tbody></table>

Returns:

any

Edit this section

<h2 id="cloudflarepagesadapteroptions">CloudflarePagesAdapterOptions</h2>
typescript
export interface CloudflarePagesAdapterOptions extends ServerAdapterOptions

Extends: ServerAdapterOptions

<table><thead><tr><th>

Property

</th><th>

Modifiers

</th><th>

Type

</th><th>

Description

</th></tr></thead> <tbody><tr><td>

functionRoutes?

</td><td> </td><td>

boolean

</td><td>

(Optional) Determines if the build should generate the function invocation routes _routes.json file.

https://developers.cloudflare.com/pages/platform/functions/routing/\#functions-invocation-routes

Defaults to true.

</td></tr> <tr><td>

staticPaths?

</td><td> </td><td>

string[]

</td><td>

(Optional) Manually add pathnames that should be treated as static paths and not SSR. For example, when these pathnames are requested, their response should come from a static file, rather than a server-side rendered response.

</td></tr> </tbody></table>

Edit this section