Repository navigation
new library public-api.ts file not using component type declared on angular.json's schematics #26981
Closed as not planned
Description
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
When I create a new library the default component inside of the lib folder takes its type from the component schematic declared on angular.json. If for example my angular.json looks like this:
{
//...
"newProjectRoot": "projects",
//...
"schematics": {
"@schematics/angular:application": {
"style": "scss",
"inlineTemplate": true,
"inlineStyle": true,
"ssr": false
},
"@schematics/angular:component": {
"changeDetection": "OnPush",
"type": "Cmp",
"inlineStyle": true,
"inlineTemplate": true,
"style": "scss"
}
}
}
After creating a library using ng generate library foo-library, the new library includes an empty dummy FooLibraryCmp inside the projects/foo-library/src/lib/foo-library.cmp.ts. However, the contents of projects/foo-library/src/public-api.ts look like this:
/*
* Public API Surface of foo-library
*/
export * from './lib/foo-library.service';
export * from './lib/foo-library.component'; // uses .component instead of .cmp
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 17.1.1
Node: 18.18.0
Package Manager: npm 9.6.6
OS: win32 x64
Angular: 17.1.1
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, ssr
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1701.1
@angular-devkit/build-angular 17.1.1
@angular-devkit/core 17.1.1
@angular-devkit/schematics 17.1.1
@schematics/angular 17.1.1
ng-packagr 17.1.2
rxjs 7.8.1
typescript 5.2.2
zone.js 0.14.3
Anything else?
No response
Activity
johalternate commentedon Jan 25, 2025
I would love to take a shot at this issue for my first contribution to angular, in fact, I already have a somewhat working solution on my fork (johalternate@ee48a80).
But Im unable to write a test for it because I cant find a way of providing default schematics config to a workspace tree created using
SchematicTestRunner.runSchematic('workspace', <some-options>).Any idea about how can I test my solution?
MeAkib commentedon Oct 18, 2026
@alan-agius4 This looks fixed on main by 661609e: the library schematic now passes type: '' to the component schematic, so a workspace-level type no longer leaks into the generated file or public-api.ts.
Can this be closed?
ChristopherPHolder commentedon Oct 26, 2026
Agree with @MeAkib, this bug was fixed in 661609e
It did not add a test case, and for this i think an e2e case would be necessary, not sure it merits it. Do something like this deserve an e2e test case?
Quick reproduction
The bug can be reproduced by running:
In the output you can see the component was generated as foo-library.cmp.ts, but public-api.ts still exports ./lib/foo-library.component:
ng build foo-library then fails with:
Quick validation
When we run the same with v20 or latest it’s not present:
the output type is what we expect:
alan-agius4 commentedon Oct 27, 2026
Thanks for taking a look at this, @MeAkib and @ChristopherPHolder! An E2E test feels a bit like overkill here, especially given how time-consuming they can be.