-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng build and ng serve with --project should clearly indicate that a project is unrecognized #17682
Closed
2 of 15 tasks
Labels
area: @angular/cli
freq1: low
Only reported by a handful of users who observe it rarely
help wanted
severity1: confusing
type: bug/fix
Milestone
Comments
kgajera
added a commit
to kgajera/angular-cli
that referenced
this issue
Jun 12, 2020
The current error message is misleading because it seems like the project exists but the target is not supported. Closes angular#17682
kgajera
added a commit
to kgajera/angular-cli
that referenced
this issue
Jun 15, 2020
Currently this falls through to a misleading error for an unsupported build target. Closes angular#17682
kgajera
added a commit
to kgajera/angular-cli
that referenced
this issue
Jun 15, 2020
Currently this falls through to a misleading error for an unsupported build target. Closes angular#17682
alan-agius4
pushed a commit
that referenced
this issue
Jun 16, 2020
Currently this falls through to a misleading error for an unsupported build target. Closes #17682
This was referenced Jun 17, 2020
Closed
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area: @angular/cli
freq1: low
Only reported by a handful of users who observe it rarely
help wanted
severity1: confusing
type: bug/fix
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Suspect that this problem has existed from day one.
Description
When running 'ng build --project ' or 'ng serve --project ', the command gives a misleading error if the project name is not recognized. In the following example, 'Typo' is a project that has not even been created.
Nothing about the error indicates that 'Typo' could not be found in the angular.json file and so starts a wild goose chase. I have been bitten by this twice at separate times when I have stepped away from the tools for a bit. A simple typo in the name of the project is enough to send one looking in the json file for errors when that is not the problem.
🔬 Minimal Reproduction
See above in the description.
🔥 Exception or Error
See above description
🌍 Your Environment
Anything else relevant?
Nope
The text was updated successfully, but these errors were encountered: