New issue
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
Issue with Component Generation Angular First App #54682
Comments
I can update the documentation and raise a PR. |
The documentation at https://angular.dev uses Angular 17, and Angular CLI 17, with the default options. With those default options, The application and the components being created are standalone: they don't use NgModule. Execute |
Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Describe the problem that you experienced
In the Video Tutorial @MarkTechson uses command -
ng generate component Home --standalone --inline-template
to generate Folder - Home.But in the document below uses the command -
ng generate component home
which fails with error - "Could not find an NgModule. Use the '--skip-import' option to skip importing in NgModule."The command in the documentation should be updated as per video instruction.
Enter the URL of the topic with the problem
https://angular.dev/tutorials/first-app/02-HomeComponent
Describe what you were looking for in the documentation
Step 1.2: To create new components named Home we should use this command -
ng generate component Home --standalone --inline-template
Add a screenshot if that helps illustrate the problem
If this problem caused an exception or error, please paste it here
The text was updated successfully, but these errors were encountered: