Skip to content
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

au run --watch stops when less code doesn't compile #382

Closed
s5no5t opened this issue Oct 19, 2016 · 0 comments
Closed

au run --watch stops when less code doesn't compile #382

s5no5t opened this issue Oct 19, 2016 · 0 comments
Labels

Comments

@s5no5t
Copy link
Contributor

s5no5t commented Oct 19, 2016

I'm submitting a bug report

Library Version:
0.21.0

Please tell us about your environment:

  • Operating System:
    Windows 10

  • Node Version:
    6.6.0

  • NPM Version:
    3.10.3

  • Language:
    Less

Current behavior:
When creating a new project using au new and choosing less as the css processor, the task au run --watch stops when there is a less file that doesn't compile (invalid syntax for example).

Expected/desired behavior:

  • create a new project with au new, select less as the css processor
  • run au run --watch
  • create a file temp.less within src/resources, containing only "{"
  • the watcher stops
  • What is the expected behavior?
    au run --watch should not stop when a less file currently doesn't compile. It should just write an error to the console.
  • What is the motivation / use case for changing the behavior?
    This breaks the otherwise extremely nice workflow of having the editor set to autosave and having the watch process run in the background, especially because you only notice it when the browser stops updating.
EisenbergEffect added a commit that referenced this issue Nov 8, 2016
Fix #382 by catching errors with gulp-plumber
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants