Error when building

[fprl]

Hi, thank you for working on this.

I can't build my app. This is my wrangler.toml:

name = "project"
main = ".worker-next/index.mjs"

compatibility_date = "2024-08-29"
compatibility_flags = ["nodejs_compat_v2"]

assets = { directory = ".worker-next/assets", binding = "ASSETS" }

This is what I get after running the command "build:worker": "cloudflare" (the project is built and I get to see the summary of the routes in the terminal)

○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand

⚙️ Copying files...

# copyPackageTemplateFiles
⚙️ Bundling the worker file...

# patchWranglerDeps
node:fs:448
    return binding.readFileUtf8(path, stringToFlags(options.flag));
                   ^

Error: ENOENT: no such file or directory, open 
'project/apps/web/.worker-next/.next/standalone/apps/web/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js'

Node.js v22.0.0

As expected, there is no file under that directory

[datagutt]

Also experiencing this, both with Next 14 and 15 (not exactly un-expected).

[jasonsilberman]

Seeing this same error with Next 13.4.19. Really excited to try this out but this is a pretty hard blocker at the moment! Fwiw I'm using yarn and saw this pr (#49), so might wait until that gets merged to try again.

[jasonsilberman]

Hi, I tried again after #49 got merged and I am still seeing this error.

[vacom]

I was waiting for the issue #45 I opened on Yarn and now I'm having this problem

[dario-piotrowicz]

Would anyone be able to provide a (hopefully minimal) reproduction for this error? that would be really really helpful 🙏

[blakeembrey]

@dario-piotrowicz I was able to reproduce by upgrading next from a fresh init in a monorepo:

mkdir mono && cd mono
echo "{\"name\":\"mono\",\"workspaces\":[\"packages/*\"],\"private\":true,\"version\":\"0.0.0\",\"description\":\"\"}" > package.json
mkdir packages && cd packages
create-cloudflare test --framework=next --experimental
cd test
npm i next@latest
npm run deploy

Error:

# patchWranglerDeps
node:fs:441
    return binding.readFileUtf8(path, stringToFlags(options.flag));
                   ^

Error: ENOENT: no such file or directory, open '/Users/blakeembrey/Projects/tmp/mono/packages/test/.worker-next/.next/standalone/packages/test/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js'

[dario-piotrowicz]

@blakeembrey thanks so much! with that I could reproduce the issue! 😄

I've also found the solution, I've got to work on something unrelated for a bit, I'll open a PR with the fix later today 🙂👍

[dario-piotrowicz]

The fix is on its way! 😄

[fprl]

Thank you a lot, next time I will add a repro for sure!

[justindjeumenet]

Hi guys!
I have the same configuration but the error comes on #patchCached:

patchCached

file:///Users/justindjeumene/WebstormProjects/xxxxxxxxx/node_modules/@opennextjs/cloudflare/dist/cli/index.mjs:6860
throw new Error("Cache patch not applied");
^
And when I read your code below, I do not know if this is coming from my side or your side:

// src/cli/build/patches/investigated/patch-cache.ts
import path7 from "node:path";
function patchCache(code, config) {
console.log("# patchCached");
const cacheHandler = path7.join(config.paths.internalPackage, "cli", "cache-handler.mjs");
const patchedCode = code.replace(
"const { cacheHandler } = this.nextConfig;",
const cacheHandler = null; CacheHandler = (await import('${cacheHandler}')).default; CacheHandler.maybeKVNamespace = process.env["${config.cache.kvBindingName}"];
);
if (patchedCode === code) {
throw new Error("Cache patch not applied");
}
return patchedCode;
}

[dario-piotrowicz]

@justindjeumenet what you're mentioning is a different bug could you please open a new issue for it? (ideally with a minimal reproduction 🙏)