Skip to content
This repository was archived by the owner on Dec 13, 2019. It is now read-only.

Log error when quasar config prep fails #101

Merged
merged 3 commits into from
Mar 26, 2018

Conversation

ovx
Copy link
Contributor

@ovx ovx commented Mar 23, 2018

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • It's submitted to the dev branch and not the master branch
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • It's been tested on Windows
  • It's been tested on Linux
  • It's been tested on MacOS
  • Any necessary documentation has been added or updated in the docs (for faster update click on "Suggest an edit on GitHub" at bottom of page) or explained in the PR's description.

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
When a quasar.conf.js contains JS errors, the build tool logs a vague message '[FAIL] quasar.conf.js has JS errors' without any specific details. This change logs out the error stack after the fail message.

Sorry, something went wrong.

ovx and others added 3 commits March 23, 2018 10:12

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@rstoenescu rstoenescu merged commit 9aa3310 into quasarframework:dev Mar 26, 2018
@rstoenescu
Copy link
Member

Thanks!

@rstoenescu
Copy link
Member

Available in CLI 0.15.15

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants