[
https://issues.apache.org/jira/browse/CB-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877829#comment-13877829
]
ASF subversion and git services commented on CB-5782:
-----------------------------------------------------
Commit 8aecd49667638b50a14709a8fa1021d0724675db in branch refs/heads/master
from [~kamrik]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=8aecd49 ]
CB-5782 Add a derived exception class for better error reporting in CLI
The on('uncaughtException') handler was removed recently in cordova-cli because
it was hiding the stack traces of some legit exceptions, but this results in
scary traces for simple errors like running outside a corodva project.
This change reintroduces the on('uncaughtException') handler and adds a special
CordovaError class for such simple errors. For exceptions of CordovaError class
only the message will be printed, for all other errors - the full stack trace.
Another pass over the code will be needed to find and convert the Errors to
CordovaErrors where appropriate. Will be done in a separate change.
> Catch exceptions and print nice error when cordova-cli run from a non cordova
> project.
> --------------------------------------------------------------------------------------
>
> Key: CB-5782
> URL: https://issues.apache.org/jira/browse/CB-5782
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
> Reporter: Michal Mocny
> Assignee: Mark Koudritsky
> Priority: Minor
>
> cordova prepare prints scary stack trace when run from the wrong directory.
> This is likely a common error and we should make it clear what is happening.
> Seems we are already catching the case, just failing to report it gracefully:
> throw new Error('Current working directory is not a Cordova-based
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
