bunx ng update ignores package manager, defaults to npm

[markgoho]

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

bunx ng update @angular/cli uses npm to install packages resulting in a package-lock.json file which otherwise wouldn't exist

Minimal Reproduction

have angular installed with bun, run bunx ng update @angular/cli see that a package-lock.json file is created because it used npm to install the update

Exception or Error

Your Environment

-terminal
Angular CLI: 20.2.2
Node: 20.19.4
Package Manager: npm 10.8.2 // probably the root of the issue, Angular doesn't know how to detect bun
OS: win32 x64
    

Angular: 20.2.3
... common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                      Version
------------------------------------
@angular-devkit/architect    0.2002.2
@angular-devkit/core         20.2.2
@angular-devkit/schematics   20.2.2
@angular/build               20.2.2
@angular/cli                 20.2.2
@angular/fire                20.0.1
@schematics/angular          20.2.2
rxjs                         7.8.2
typescript                   5.9.2

Anything else relevant?

No response

[JoostK]

This is likely because of https://bun.com/blog/bun-lock-text-lockfile, where Bun has switched from bun.lockb to bun.lock, whereas the CLI only tests for the presence of the binary lock file.

You can work around it by setting an explicit packageManager in angular.json.