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
Documentation is lacking #11847
Comments
+1 to all of that. We're working on it! A few things that will help:
|
It would be great if the config for
This seems to pull in versions of dependencies across 0.7.3 0.7.4 6.1.3 and 6.1.4 Am I actually just supposed to put in |
Closing, since the CLI docs are now officially here: https://angular.io/cli/, the @thepian, this page clarifies a few things: https://angular.io/guide/npm-packages -- not sure if it's what you were after. If not, might be worth opening a more specific issue. |
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. |
Bug Report or Feature Request (mark with an
x
)Versions
Desired functionality
The documentation of the CLI is tremendously lacking. This is not the first issue talking about it and, until the problem is properly addressed, it won't be the last. Here are some of the problems I've come across:
Example:
ng serve
is said to have a--verbose
option, but when I runng serve --verbose
, I get an error: "Unknown option: '--verbose'". If an option as simple asverbose
is improperly documented, how can I trust anything else on the wiki? When I'm confronted with a problem, how do I know whether I made a mistake or the documentation mislead me?Sure it's good to have, but it doesn't actually explain much, especially when the description of each option doesn't provide any useful info. Example: the description of
ng build
's--configuration
option is "Specify the configuration to use."Why are there stories for Angular Material, Font Awesome and other libraries ? The stories that actually relate to the CLI, like "Multiple projects" are more difficult to spot, especially since they are listed in no meaningful order. Stories are also not a replacement for proper documentation of commands, options and workflows.
The text was updated successfully, but these errors were encountered: