Closed jestanoff closed 7 years ago
Hey @jestanoff, did you ever get this resolved?
I can't see anything wrong in the code above.
@OverZealous, it is still not fixed. Let me explain it this way, the cachebust:replace task should rename all asset hashes only after all of these are available. However what happens is that task exits prematurely.
Is there any way to debug runSequence so I know what is the exit status of each task?
The only other thing I can guess is one of your other tasks isn't returning properly (so it's not running asynchronously).
(Generally speaking, Gulp is designed so that you'd do your "cache-busting" inside a file stream, rather than as a separate step. That's where we do ours—the dist
version of our scripts handle adding the rev tag and replacing the dev filenames inline with the normal processing.)
Closing because I'm confident this is due to an improper task setup, where a gulp task is correctly configured for asynchronous processes, which causes the following task to run prematurely.
I haven't included all tasks as the file is way too long.
I'm having problems with
cachebust:replace
above, which when run in sequence takes 939ms and doesn't complete the full length of the task. However when I run it on its own it takes 4s and completes just fine.