Skip to content

Issue with export paths when library generated using angular cli #30886

@gchalamasetty

Description

@gchalamasetty

Command

generate

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

Description

When a library is generated using ng generate library, there is an Issue/bug with export path of the library module in public-api.ts.

Minimal Reproduction

To reproduce this issue:

  1. Go to this stackblitz project
  2. Open new terminal and run ng generate library lib-gen-test --standalone=false
  3. After library is successfully created, go to public-api.ts file of the new library and notice the issue with export module statement.

New library name: "lib-gen-test, you should see a lib-gen-test.module.ts file created in the library.

Expectation:
I should see export * from './lib/lib-gen-test.module'; in public-api.ts file.

Current Behavior/Issue:
I see export * from './lib/lib-gen-test-module'; in public-api.ts file.

Instead of dot(.) i am seeing a dash(-) in module path.

Exception or Error


Your Environment

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
rxjs                         7.8.2
typescript                   5.8.2
zone.js                      0.15.0

Anything else relevant?

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions