We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate
When I build angular library with Secondary Entry Points in a sample layout as below:
my_package ├── src | ├── public_api.ts | └── *.ts ├── ng-package.json ├── package.json └── testing ├── src | ├── public_api.ts | └── *.ts └── ng-package.json
I need to use ng g command under main entry point and Secondary Entry Points. But the command just works with "src\lib" as base path.
ng g
Could you provide "base-path" parameter with ng g command.
No response
The text was updated successfully, but these errors were encountered:
Hey, let’s continue tracking the generation of second entry-points in #19070.
ng g library is definitely not intended to be used to generate a secondary entry-point, as it creates and Angular library project inside a workspace.
ng g library
Sorry, something went wrong.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
No branches or pull requests
Command
generate
Description
When I build angular library with Secondary Entry Points in a sample layout as below:
I need to use
ng g
command under main entry point and Secondary Entry Points. But the command just works with "src\lib" as base path.Describe the solution you'd like
Could you provide "base-path" parameter with
ng g
command.Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: