Build failing due to forced lockfile on dependencies

For Workers & Pages, what is the name of the domain?

  • hasn’t built yet

What is the issue or error you’re encountering

08:18:05.613Initializing build environment…08:18:14.335Success: Finished initializing build environment08:18:14.960Cloning repository…08:18:16.016Detected the following tools from environment: [email protected], [email protected], [email protected]:18:16.017Installing project dependencies: bun install --frozen-lockfile08:18:16.241bun install v1.1.33 (247456b6)08:18:16.286Resolving dependencies08:18:16.839Resolved, downloaded and extracted [56]08:18:16.843error: lockfile had changes, but lockfile is frozen08:18:16.843note: try re-running without --frozen-lockfile and commit the updated lockfile08:18:16.849Failed: error occurred while installing tools or dependencies

What steps have you taken to resolve the issue?

Added explitely to the .TOML file to avoid lockfiles, added in the build commadn to avoid lockfiles, added variables in the setings to avoid lockfiles, but ntohing seems to work and it kepe adding it to the build.

I’m using lovable.dev to sync to Github and then that is syncing to Cloudflare.

Any help would be grealty appreciate, but im about ot give up on cloudflare pages at this point :stuck_out_tongue:

Screenshot of the error

I have the same issue; lovable to github to cloudflare failing with error: lockfile had changes, but lockfile is frozen

Hey @christopherjvanek I had exactly the same problem and solved it by realizing I had accidentally set up a Worker, not a Page. Remove the Worker in Cloudflare and start over with “Add New” or whatever it is, being very careful to select Page when you get to it. From there it was pretty easy.

2 Likes

This was it, I’ve since fixed this now today and this was the issue! Due to being a worker clousflare was doing some funky things.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.