Deployment Issues on Cloudflare Pages with SvelteKit 5

[rastislavcore]

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"
   

   The index.ts exports components from specific folders, such as 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"
   

   Similar to the first project, the 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, TypeScript type definitions, and component structures have been verified, and Cloudflare-specific configurations (e.g., wrangler.toml) align with the projects’ requirements.

Questions for the Community:

1. Are there known limitations or nuances with the 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 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!

[userquin]

can you try removing/disabling the pwa plugin in CF to test the build without the plugin? the buildEnd hook in the pwa build plugin just re-throw the error if present:

• https://github.com/vite-pwa/vite-plugin-pwa/blob/main/src/plugins/build.ts#L54-L57

[rastislavcore]

Not related to plugin itself. Analyzing the issue further.