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
running shifter ---watch on a module with an exec command in the build.json (one which writes module js that needs to be shifted) causes shifter to go into a loop.
Shifter in building the module runs the command in the exec property, then sees that the module source js has been changed (by the script in the exec) and starts building again, ad infinitum.
We need the mtime check, because sometimes the size can stay the same, like when you correct a typo or something. It's annoying to write a few unneeded characters only to kick start a build.
running
shifter ---watch
on a module with anexec
command in the build.json (one which writes module js that needs to be shifted) causes shifter to go into a loop.Shifter in building the module runs the command in the
exec
property, then sees that the module source js has been changed (by the script in the exec) and starts building again, ad infinitum.At line 74 of watch.js there's a check against mtime which if removed solves the issue, but I guess that would miss a changed file that was coincidently the same size?
https://github.com/yui/shifter/blob/master/lib/watch.js#L74
The text was updated successfully, but these errors were encountered: