1 reply

Deployment Issues on Cloudflare Pages with SvelteKit 5

We are encountering issues while deploying two separate SvelteKit 5 projects to Cloudflare Pages. The build process fails with errors related to resolving component paths or modules. Here are the details of the issues:

1. Project 1: DApp SvelteKit Boilerplate
Error:

   [vite-plugin-pwa:build] Could not resolve "./icon" from "src/lib/components/index.ts"

   [vite-plugin-pwa:build] Could not resolve "./icon" from "src/lib/components/index.ts"

The

index.ts

index.ts

exports components from specific folders, such as

export { Icon } from './icon';

export { Icon } from './icon';

, but the PWA plugin cannot resolve the path despite no issues in local development.

2. Project 2: PayTo
Error:

   Could not resolve "./Toast.svelte" from "src/lib/components/toast/index.ts"

   Could not resolve "./Toast.svelte" from "src/lib/components/toast/index.ts"

Similar to the first project, the

index.ts

index.ts

files structure components, and the issue arises when the PWA plugin fails to resolve paths during the Cloudflare build process.

Both projects work correctly in local environments, including full SSR builds, but they consistently fail on Cloudflare Pages. Key configurations such as

vite.config.ts

vite.config.ts

, TypeScript type definitions, and component structures have been verified, and Cloudflare-specific configurations (e.g.,

wrangler.toml

wrangler.toml

) align with the projects’ requirements.

Questions for the Community:
1. Are there known limitations or nuances with the

vite-plugin-pwa

vite-plugin-pwa

or Rollup on Cloudflare Pages that could be causing these resolution issues?
2. Could the problem be related to the

wrangler.toml

wrangler.toml

setup, Cloudflare's filesystem structure, or case sensitivity in component folder names?
3. Is there a recommended debugging approach to further isolate issues specific to Cloudflare’s environment?

Any insights or similar experiences would be greatly appreciated!

GitHub

Drizzle ORM by rastislavcore · Pull Request #13 · bchainhub/dapp-sv...

GitHub

Refactor components by rastislavcore · Pull Request #39 · bchainhub...

Cloudflare Developers•16mo ago•

1 reply

Rastislav₡ore

Deployment Issues on Cloudflare Pages with SvelteKit 5

   [vite-plugin-pwa:build] Could not resolve "./icon" from "src/lib/components/index.ts"

   [vite-plugin-pwa:build] Could not resolve "./icon" from "src/lib/components/index.ts"

The

index.ts

index.ts

exports components from specific folders, such as

export { Icon } from './icon';

export { Icon } from './icon';

, but the PWA plugin cannot resolve the path despite no issues in local development.

2. Project 2: PayTo
Error:

   Could not resolve "./Toast.svelte" from "src/lib/components/toast/index.ts"

   Could not resolve "./Toast.svelte" from "src/lib/components/toast/index.ts"

Similar to the first project, the

index.ts

index.ts

vite.config.ts

vite.config.ts

, TypeScript type definitions, and component structures have been verified, and Cloudflare-specific configurations (e.g.,

wrangler.toml

wrangler.toml

) align with the projects’ requirements.

Questions for the Community:
1. Are there known limitations or nuances with the

vite-plugin-pwa

vite-plugin-pwa

or Rollup on Cloudflare Pages that could be causing these resolution issues?
2. Could the problem be related to the

wrangler.toml

wrangler.toml

GitHub

Drizzle ORM by rastislavcore · Pull Request #13 · bchainhub/dapp-sv...

GitHub

Refactor components by rastislavcore · Pull Request #39 · bchainhub...

Deployment Issues on Cloudflare Pages with SvelteKit 5

Deployment Issues on Cloudflare Pages with SvelteKit 5

Similar Threads

Similar Threads

Similar Threads