I'm using Bun, it's specified on package.json, but pages tries to download with npm
Hey, I have a NextJS website that I'm trying to deploy to cf pages. I could to it through wrangler, but I want to have builds on pushes, so I want to build through cf. I'm using Bun, and it's specified in the package.json, but for some reason, cf decides to run npm install, and fails.
package.json
9 Replies
CF Pages logs:
Thank you in advance 😄
does a package-lock.json exist?
nop
only the bun one
let me send you some screenshots
ls on root
ls on apps/nextjs
it's a monorepo
I'll try to force it to use pnpm instead of bun
and see if it changes anything
Hey @Erisa (sorry for the ping 🙏), still happening on another project, same issue. Pages installs bun, and then proceeds to use npm install. I recreated it accidentally using a monorepo with bun, and setting the
Root directory
. Should I report it somewhere?
I guess is that it initially detects bun lockfile, but when proceeds to install, it doesn't detect the lockfile on the set root directory (since there is none, it's a monorepo)Yeah this is happening for me too
@Pol @Jeff did you set build command in CF Workers UI?
did you manage to solve this @Pol ?
I ended up using pnpm, since it's more reliable, and just install bun as a package for some stuff