Migrating from yarn to bun bug

[alessiotortora]

What version of Bun is running?

bun@1.1.43

What platform is your computer?

Darwin 24.1.0 arm64 arm

What steps can reproduce the bug?

Migrated from yarn to bun. so im not using yarn anymore

bun works but it gives this error:

$ next dev
  ▲ Next.js 14.2.1
  - Local:        http://localhost:3000
  - Environments: .env

 ✓ Starting...
error This project's package.json defines "packageManager": "yarn@bun@1.1.43". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
 ✓ Ready in 1306ms

What is the expected behavior?

  "packageManager": "bun@1.1.43",

What do you see instead?

No response

Additional information

No response

[Aram1d]

The error seems clear enough:

You should remove the packageManager field from your package.json.
For a full cleanup:

• verify you have no .yarn folder (delete it if present).
• delete package-lock.json
• delete node_modules

run bun install to recreate your node_modules dependency folder.
You should now have a bun.lockb file instead of package-lock.json

[alessiotortora]

The error seems clear enough:

You should remove the packageManager field from your package.json. For a full cleanup:

• verify you have no .yarn folder (delete it if present).
• delete package-lock.json
• delete node_modules

run bun install to recreate your node_modules dependency folder. You should now have a bun.lockb file instead of package-lock.json

I tried this already.
Im using a monorepo and packageManager is required.

i deleted all yarn files, yarn lock, yarn cache etc
deleted node_modules, .next , etc

tried a new project and copied everything seperate back into the new project, same error.

Bun works, i can do everything with bun. Just on restart this error comes that the package manager sees yarn@bun@1.1.43.
but everything works.

[JasonLovesDoggo]

The error seems clear enough:
You should remove the packageManager field from your package.json. For a full cleanup:

• verify you have no .yarn folder (delete it if present).
• delete package-lock.json
• delete node_modules

run bun install to recreate your node_modules dependency folder. You should now have a bun.lockb file instead of package-lock.json

I tried this already. Im using a monorepo and packageManager is required.

i deleted all yarn files, yarn lock, yarn cache etc deleted node_modules, .next , etc

tried a new project and copied everything seperate back into the new project, same error.

Bun works, i can do everything with bun. Just on restart this error comes that the package manager sees yarn@bun@1.1.43. but everything works.

I got the same issue migrating from pnpm to bun on a turborepo project

error This project's package.json defines "packageManager": "yarn@bun@1.1.30". However the current global version of Yarn is 1.22.22.

[alessiotortora]

The error seems clear enough:
You should remove the packageManager field from your package.json. For a full cleanup:

• verify you have no .yarn folder (delete it if present).
• delete package-lock.json
• delete node_modules

run bun install to recreate your node_modules dependency folder. You should now have a bun.lockb file instead of package-lock.json

I tried this already. Im using a monorepo and packageManager is required.

i deleted all yarn files, yarn lock, yarn cache etc deleted node_modules, .next , etc

tried a new project and copied everything seperate back into the new project, same error.

Bun works, i can do everything with bun. Just on restart this error comes that the package manager sees yarn@bun@1.1.43. but everything works.

I got the same issue migrating from pnpm to bun on a turborepo project

error This project's package.json defines "packageManager": "yarn@bun@1.1.30". However the current global version of Yarn is 1.22.22.

Did you find a solution ? Did you try to uninstall pnpm globally ?