If the task fails, newer-postrun:... never gets called #81
Comments
|
Can you provide an example that demonstrates a problem. |
guncha
added a commit
to guncha/grunt-newer-conf-corruption
that referenced
this issue
May 30, 2015
To reproduce tschaub/grunt-newer/issues/81: 0) npm install 1) grunt newer:coffee 2) grunt watch 3) add 'super' keyword to hello.coffee, this will break the build 4) fix hello.coffee by removing 'super' 5) touch world.coffee, newer:coffee doesn't see that it has changed
|
Just pushed a repo that demonstrates the problem. Instructions are in the commit message. Hope that helps. |
|
@tschaub, did you manage to confirm it? |
|
I'm having this problem frequently in a similar build configuration, and can confirm that #80 fixes it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was a fun one. On https://github.com/tschaub/grunt-newer/blob/master/tasks/newer.js#L133, when
grunt-newerasks for the tasks to be run, if the first task fails for whatever reason,newer-postrunnever gets run, the config is not restored and a lot of bad things happen.For me it manifested as a multi target task stopped working via newer as the config was corrupted. This can be worked around using
--forcecommand line option, but I don't know enough about grunt to make the necessary changes.The text was updated successfully, but these errors were encountered: