Hello guys, I hit error when build the pages today - but it was fine last time ``` 10:46:05.883

Hello guys, I hit error when build the pages today - but it was fine last time

10:46:05.883     WARN  Ignoring not compatible lockfile at /opt/buildhome/repo/pnpm-lock.yaml
10:46:05.885     ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is absent
10:46:05.885    
10:46:05.886    Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"
10:46:05.917    Error: Exit with error code: 1
10:46:05.917        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
10:46:05.917        at Object.onceWrapper (node:events:652:26)
10:46:05.917        at ChildProcess.emit (node:events:537:28)
10:46:05.917        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
10:46:05.927    Failed: build command exited with code: 1
10:46:06.645    Failed: error occurred while running build command

10:46:05.883     WARN  Ignoring not compatible lockfile at /opt/buildhome/repo/pnpm-lock.yaml
10:46:05.885     ERR_PNPM_NO_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is absent
10:46:05.885    
10:46:05.886    Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"
10:46:05.917    Error: Exit with error code: 1
10:46:05.917        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
10:46:05.917        at Object.onceWrapper (node:events:652:26)
10:46:05.917        at ChildProcess.emit (node:events:537:28)
10:46:05.917        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
10:46:05.927    Failed: build command exited with code: 1
10:46:06.645    Failed: error occurred while running build command

15 Replies

Unknown User•7mo ago

Message Not Public

Dalist•7mo ago

guys, can we please bump the default node version to 20?

Unknown User•7mo ago

Message Not Public

Ricky U•7mo ago

Hi, Having a pretty strange and urgent problem, we accidently ornage cloudled a CNAME for a third party api, which logs in and out users, which caused errors, and now turned it back off. Some routes to the CNAME are OK,but others are failing with a 301 redirect? i scrapped all the cache, but some cname endpoints are still failing with CORS, i dont think its a cors at all, sometimes the browser will return this error, -- what can i do?

Phillip•7mo ago

None of my pages are building anymore:

The package "async_hooks" wasn't found on the file system but is built into node. Are you trying
to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

The package "async_hooks" wasn't found on the file system but is built into node. Are you trying
to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

last time i deployed was < 5 days ago but i just ran through all of them and none can be built. My typical script is:

bunx @cloudflare/next-on-pages
bunx wrangler pages deploy .vercel/output/static --project-name=xxxxx

bunx @cloudflare/next-on-pages
bunx wrangler pages deploy .vercel/output/static --project-name=xxxxx

Walshy•7mo ago

https://community.cloudflare.com/t/could-not-resolve-async-hooks/741456/12?u=walshy Vercel broke next-on-pages, team is aware - you can resolve for now through the recommendation there

Phillip•7mo ago

Of course they did 🙂 Works thanks @Walshy

Snow•7mo ago

Does redirection rules not work for a domain on cloudflare pages?

Zack•7mo ago

Hey, I am unsure if this is related to the currently ongoing issues with pages and workers deployments, but I am seeing an issue when adding a custom domain to pages via the API, it is claiming the domain already exists for the project. I have verified this a couple times by deleting the domain and then sending the request again, it's the same every time. The custom domain gets created but the API responds with this error

error creating domain for project "abc123": You have already added this custom domain. Select another custom domain or check your project configuration. (8000018)

Zack•7mo ago

Probably also related, when trying to delete that custom domain to attempt the test again, the API throws a 500 error

Zack•7mo ago

It seems re-creating the entire pages project solved the problem, so maybe some after effect of the issues from earlier

ethereon•7mo ago

is cloudflare down rn? im having a domain issue too it deploys to pages but not my domain

1984 Ford Laser•7mo ago

no lol this server would be on fire if so

ethereon•7mo ago

why's my domain not getting deployed to?

1984 Ford Laser•7mo ago

Are you using Next.js at all?

Gaming

Programming

Hello guys, I hit error when build the pages today - but it was fine last time ``` 10:46:05.883

Did you find this page helpful?