service core:user:my-react-app: Uncaught Error: No such module

[brillout]

What versions & operating system are you using?

System:
OS: Linux 6.8 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Memory: 2.70 GB / 7.52 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
npmPackages:
@cloudflare/vite-plugin: https://pkg.pr.new/@cloudflare/vite-plugin@31c94b7 => 1.9.5
wrangler: https://pkg.pr.new/wrangler@31c94b7 => 4.24.4

Please provide a link to a minimal reproduction

https://github.com/brillout/repro_vite-plugin-cloudflare_no-such-module

Describe the Bug

An unexpected error is thrown:

service core:user:my-react-app: Uncaught Error: No such module "dist/server/chunks/chunk-DgBTj3OE.js".
  imported from "dist/server/entries/pages_about.mjs"

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at _Miniflare.#assembleAndUpdateConfig (/home/rom/tmp/repro_vite-plugin-cloudflare_no-such-module/node_modules/.pnpm/miniflare@https+++pkg.pr.new+cloudflare+workers-sdk+miniflare@31c94b7/node_modules/miniflare/src/index.ts:2028:10)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at Mutex.runWith (/home/rom/tmp/repro_vite-plugin-cloudflare_no-such-module/node_modules/.pnpm/miniflare@https+++pkg.pr.new+cloudflare+workers-sdk+miniflare@31c94b7/node_modules/miniflare/src/workers/shared/sync.ts:66:45)

The file dist/server/chunks/chunk-DgBTj3OE.js does exist and the import path inside dist/server/entries/pages_about.mjs is correct.

See reproduction.

Please provide any relevant error logs

No response

[jamesopstad]

When I look at the main field in dist/server/wrangler.json, it is set to entries/pages_about.mjs, which I don't think is correct. What file should this point to? There should be a single entry file and other JS files that it imports need to not be above it in the file hierarchy.

[brillout]

The production entry is the user file worker/index.ts. (Because the reproduction isn't using vike-server — see also vikejs/vike#562 Transpile server code and vite-plugin-server-entry in case you're curious.)

I updated the reproduction to also build worker/index.ts (brillout/repro_vite-plugin-cloudflare_no-such-module@6f572cc).

If I manually change dist/server/wrangler.json to the following:

- "main": "entries/pages_about.mjs",
+ "main": "../worker/index.js",

Then I get another error:

service core:user:my-react-app: Uncaught Error: No such module "dist/worker/vike/server".
  imported from "dist/worker/ssr.js"

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at _Miniflare.#assembleAndUpdateConfig (/home/rom/tmp/repro_vite-plugin-cloudflare_no-such-module/node_modules/.pnpm/miniflare@https+++pkg.pr.new+cloudflare+workers-sdk+miniflare@31c94b7/node_modules/miniflare/src/index.ts:2028:10)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at Mutex.runWith (/home/rom/tmp/repro_vite-plugin-cloudflare_no-such-module/node_modules/.pnpm/miniflare@https+++pkg.pr.new+cloudflare+workers-sdk+miniflare@31c94b7/node_modules/miniflare/src/workers/shared/sync.ts:66:45)

It seems that Workers runtime cannot resolve non-relative imports?

// Seems like the Workers runtime interpret 'vike/server' as a relative path
import { renderPage } from 'vike/server'

[jamesopstad]

I updated the reproduction to also build worker/index.ts (brillout/repro_vite-plugin-cloudflare_no-such-module@6f572cc).

If I manually change dist/server/wrangler.json to the following:

• "main": "entries/pages_about.mjs",

• "main": "../worker/index.js",
  Then I get another error:

service core:user:my-react-app: Uncaught Error: No such module "dist/worker/vike/server".
  imported from "dist/worker/ssr.js"

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at _Miniflare.#assembleAndUpdateConfig (/home/rom/tmp/repro_vite-plugin-cloudflare_no-such-module/node_modules/.pnpm/miniflare@https+++pkg.pr.new+cloudflare+workers-sdk+miniflare@31c94b7/node_modules/miniflare/src/index.ts:2028:10)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at Mutex.runWith (/home/rom/tmp/repro_vite-plugin-cloudflare_no-such-module/node_modules/.pnpm/miniflare@https+++pkg.pr.new+cloudflare+workers-sdk+miniflare@31c94b7/node_modules/miniflare/src/workers/shared/sync.ts:66:45)

It seems that Workers runtime cannot resolve non-relative imports?

// Seems like the Workers runtime interpret 'vike/server' as a relative path
import { renderPage } from 'vike/server'

But now you're building the entry file completely separately from Vite. What would you expect vike/server to resolve to in the output bundle?

[brillout]

I further updated the repro to bundle the worker into a single file (brillout/repro_vite-plugin-cloudflare_no-such-module@4d1efab).

It now works!

But I still need to manually change dist/server/wrangler.json to the following:

- "main": "entries/pages_about.mjs",
+ "main": "../worker/index.js",

I couldn't find a configuration for this while looking at the TypeScript declaration of @cloudflare/vite-plugin. Is there a way I can configure the main entry of dist/server/wrangler.json?

What would you expect vike/server to resolve to in the output bundle?

I guess the bottom line is that wrangler doesn't upload the whole node_modules/ directory. Thus all import paths must be relative. (I don't know whether another round of building happens or not — I guess not.)

[brillout]

(In case you're curious — the following is out-of-topic.)

But now you're building the entry file completely separately from Vite.

This is by design: Vike allows the user to manually integrate the server on his own (see for example https://vike.dev/cloudflare#manual-integration). The user then must build his server separately and independently from Vike (but he can use tools such as vite-node and vavite which use Vite.)

Instead of manually integrating the server, the user can use vike-server (powered by the Nitro alternative called Photon) in which case Vike takes care of everything and the user's server code is built with Vite — like other Vite-based frameworks.

It's part of Vike's vision: a framework powered by a modular architecture, so that the user can use Nitro, Photon, or go for a completely bespoke server integration.

[jamesopstad]

I couldn't find a configuration for this while looking at the TypeScript declaration of @cloudflare/vite-plugin. Is there a way I can configure the main entry of dist/server/wrangler.json?

We determine the main value automatically based on the entry chunk in the bundle. See here. Is there a way you can make it so that the Worker entry is the entry chunk in Vite's build output?

I guess the bottom line is that wrangler doesn't upload the whole node_modules/ directory. Thus all import paths must be relative. (I don't know whether another round of building happens or not — I guess not.)

That's correct. All code must be bundled. It doesn't have to bundled into a single file but there must be a single entry file.

[jamesopstad]

Instead of manually integrating the server, the user can use vike-server (powered by the Nitro alternative called Photon) in which case Vike takes care of everything and the user's server code is built with Vite — like other Vite-based frameworks.

I think this is the approach the makes sense with the Cloudflare plugin as it is based on the server code being built by Vite.

[brillout]

I think this is the approach the makes sense with the Cloudflare plugin as it is based on the server code being built by Vite.

Our primary goal is to integrate @cloudflare/vite-plugin in the context of users using vike-server / Photon.

The reproduction's setup (which doesn't use vike-server / Photon) is based on a playground I use internally to test the changes necessary on Vike's side. It won't be something we recommend to users.

That the user can go for a custom integration without using vike-server / Photon is just a nice-to-have. Whether @cloudflare/vite-plugin wants to support this kind of setup is up to the Cloudflare team. (IMO it could be worth it, since the only change needed would be a new setting to set the value of wrangler.json#main, but I understand that you might want to keep the configuration minimal.)

We determine the main value automatically based on the entry chunk in the bundle. See here. Is there a way you can make it so that the Worker entry is the entry chunk in Vite's build output?

Since the worker isn't processed by Vite it isn't an option (unless I create some kind of fake entry). But it's okay — I can just patch dist/server/wrangler.json in a post-build script.

---

Closing as this isn't blocking us anymore. Thank you for the helpful discussion!