Closed TheDancingCode closed 3 years ago
Nope, this is not yet good enough. gulp-run still depends on vinyl 0.4.6, which (from what i gathered) caused the whole ordeal first place. It's also possible that the vinyl test fails for that very reason. I haven't tried yet, but upgrading to vinyl 2.1 might fix the issue.
I agree with line0. I would suggest the following: we find out if vinyl
is the problem - if so, we should try to update the dependency. If that does not solve the problem, we can consider making a new major release for gulp-run.
I just tried to look into this, and I found that the current master branch is failing tests as well.
The goal of this PR is not to fix issues you previously might have had with your plugin. It simply replaces a deprecated utility package by a functionally equivalent but smaller one. If the tests were failing before, they still will do so now, but the problem is unrelated to the PR or the changes it proposes.
I don't know the inner workings or the history of your package, so I'm not sure what the 'whole ordeal' is that you're referring to. So if this is 'not yet good enough', I'm afraid I can't help out any further. But once again, this PR is not trying to fix any and all problems you have with your plugin.
The "while ordeal" he's referring to is that the outdated vinyl
package is the cause of gulp-util
breakage.
Here's a reference to why gulp-util
is breaking packages in gulp v4: https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
Any progress on this?
Is there any update over two years later?
Closes #53