You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ng [command] --help does not work outside angular project folder for some commands聽#19057
Command that does not work for in case of global cli marked with an x
new
[ x] build
[ x] serve
[ x] test
[ x] e2e
[ x] generate
[ x] add
update
[ x] lint
[ x] xi18n
[ x] run
config
help
version
doc
Is this a regression?
Yes
Description
Help info should be available for any angular-cli related command regardless you inside angular-cli project folder (local cli) or outside angular-cli project folder (global cli)
馃敩 Minimal Reproduction
Navigate outside angular-cli project in console then run any below command:
ng build --help
ng serve --help
ng test --help
ng e2e --help
ng generate --help
ng add --help
ng lint --help
ng xi18n --help
ng run --help
馃敟 Exception or Error
Getting error: /private/var/folders/jj/sjmtmgms0d73pgpp6xqjgq480000gn/T/ng-UIzJTX/angular-errors.log" for further details.
Here is cat angular-errors.log:
[error] Error: Unable to locate a workspace file for workspace path.
at Object.readWorkspace (/Users/Name/.nvm/versions/node/v12.18.4/lib/node_modules/@angular/cli/node_modules/@angular-devkit/core/src/workspace/core.js:75:19)
at async RunCommand.initialize (/Users/Name/.nvm/versions/node/v12.18.4/lib/node_modules/@angular/cli/models/architect-command.js:31:31)
at async RunCommand.validateAndRun (/Users/Name/.nvm/versions/node/v12.18.4/lib/node_modules/@angular/cli/models/command.js:124:9)
at async Object.runCommand (/Users/Name/.nvm/versions/node/v12.18.4/lib/node_modules/@angular/cli/models/command-runner.js:198:24)
at async default_1 (/Users/Name/.nvm/versions/node/v12.18.4/lib/node_modules/@angular/cli/lib/cli/index.js:59:31)
Activity
alan-agius4 commentedon Oct 13, 2020
Duplicate of #16241
angular-automatic-lock-bot commentedon Nov 13, 2020
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.