Command

build

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

19.2.14

Description

I'm trying to upgrade the ngx-speculoos library from v19 to v20, and chose to use the new builder during the migration. Here's a link to the changes that the update procedure and I did to migrate:

https://github.com/Ninja-Squad/ngx-speculoos/pull/402/files

I also tried to adopt the new way of referencing projects in the tsconfig file, if that matters.

Since that change however, the file index.d.ts file generated by ng build --project ngx-speculoos does not include the jasmine matchers that are supposed to be generated from this import, referencing this file.

It used to work fine before the upgrade. The build used to generate the following files (among others):

• index.d.ts, which exported everything from public_api;
• public_api.d.ts, which imported './jasmine-matchers' and exported everything from a bunch of other files;
• jasmine-matchers.d.ts, defining the additional matchers

After the upgrade, the build only has an index.d.ts, where doesn't contain any sign of the jasmine matchers.

Minimal Reproduction

git clone [email protected]:Ninja-Squad/ngx-speculoos.git
git checkout chore/ng20
pnpm i
pnpm ng build --project ngx-speculoos

Exception or Error

Your Environment

Angular CLI: 20.0.0
Node: 20.19.2
Package Manager: pnpm 10.11.0
OS: darwin x64

Angular: 20.0.0
... build, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.2000.0
@angular-devkit/core         20.0.0
@angular-devkit/schematics   20.0.0
@schematics/angular          20.0.0
ng-packagr                   20.0.0
rxjs                         7.8.2
typescript                   5.8.3
zone.js                      0.15.1

Anything else relevant?

No response