-
Notifications
You must be signed in to change notification settings - Fork 12k
ng build --watch does not work after adding a lib to the workspace #23291
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
Comments
…termined When the workspace has multiple projects and we the project to use cannot be determined from the current working directory, we now issue an actionable error message. Closes angular#23291
…termined When the workspace has multiple projects and we the project to use cannot be determined from the current working directory, we now issue an actionable error message. Closes angular#23291
…termined When the workspace has multiple projects and we the project to use cannot be determined from the current working directory, we now issue an actionable error message. Closes angular#23291
…termined When the workspace has multiple projects and we the project to use cannot be determined from the current working directory, we now issue an actionable error message. Closes angular#23291
…termined When the workspace has multiple projects and we the project to use cannot be determined from the current working directory, we now issue an actionable error message. Closes angular#23291
…termined When the workspace has multiple projects and we the project to use cannot be determined from the current working directory, we now issue an actionable error message. Closes angular#23291
@alan-agius4 I already provide the project via |
Interesting, |
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes angular#23291
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes angular#23291
Should be addressed via c9a2d4e |
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes angular#23291
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes angular#23291
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes angular#23291
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes angular#23291
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes angular#23291
Yargs allows passing using positional arguments as flags. This we should handle this when retrieving the project. Closes #23291
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
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was: 13.3.7Description
When creating an empty workspace and adding an application, the
ng build --watch
command works as expected. After adding a library to the workspace it does not work anymore. Running the command will throw the following error:🔬 Minimal Reproduction
ng new watchdemo --create-application=false
cd watchdemo
ng generate app showcase
--project=showcase
to the build + watch scripts in package.jsonnpm run build
andnpm run watch
=> worksng generate lib comp
npm run build
=> works (builds the showcase app)npm run watch
=>Error: Unknown argument: watch
Repo Angular 14: https://github.com/rothsandro/repro-ng-cli-watch-14/
Repo Angular 13 (works): https://github.com/rothsandro/repro-ng-cli-watch-13/
🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
The text was updated successfully, but these errors were encountered: