Bun not working

[euskadi31]

Command

update

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

I'm trying to use ng update in an Angular project in a monorepo

Contexte:
I use monorepo, the bun.lock is in the parent (root workspace), the Angular is in the console/ directory.

.
├── bun.lock
├── console
│   ├── README.md
│   ├── angular.json
│   ├── components.json
│   ├── dist
│   ├── libs
│   ├── package.json
│   ├── public
│   ├── src
│   ├── tsconfig.app.json
│   ├── tsconfig.json
│   └── tsconfig.spec.json
├── node_modules
├── package.json

Minimal Reproduction

1. Create a new Angular project with npm in menorepo (console/)
2. Migrate npm to bun (change cli.packageManager to bun in angular.json)
3. Run bunx ng update @angular/cli in console/

Exception or Error

bunx ng update @angular/cli
The installed Angular CLI version is outdated.
Installing a temporary Angular CLI versioned 21.2.2 to perform the update.
Using package manager: bun
Collecting installed dependencies...
Found 4 dependencies.
Package '@angular/cli' is not a dependency.

Your Environment

Bun: 1.3.10
Angular cli: 21.2.0 
OS: macOS 26.3

Anything else relevant?

No response

[alan-agius4]

@euskadi31, I am not able to reproduce this.

bunx ng update @angular/cli
Using package manager: bun
Collecting installed dependencies...
Found 15 dependencies.
Fetching dependency metadata from registry...
Package '@angular/cli' is already up to date.

Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

[jsangmeister]

I assume that this is unrelated to bun and instead to the directory structure, as it's the same error for me in #32787 with npm.