I never used Webpack, I prefer Gulp because it just run tasks and listen to me when I want to do X when Y. I do not like all the magic and I prefer to know which tool do what when, so Gulp is my go to.
I happened to maintain old projects that I did some months ago, and going from Gulp 3 to 4 was a breeze.
I think in the end if you try to go progressive, and test everything like a psycopath even if you just add this tiny little package you might be able to locate the source of the issue earlier, but I generally have the feeling like you that build tools have made our lives more complicated (mostly if you are not a full front-end developer that does other things like keeping up with all those build tools releases and features).
I'm actually also refactoring our old Gulp projects to Webpack because they have become completely outdated and only throw errors.
Instead of debugging the whole thing I just update it to the latest and greatest.
The biggest cause is updating the node and npm versions on my machine of course.
So in a way it's my own fault.
Maybe this is why agencies often have their own virtual machine where they control versioning for all developers instead of lettings the developers update it whenever they want.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I never used Webpack, I prefer Gulp because it just run tasks and listen to me when I want to do X when Y. I do not like all the magic and I prefer to know which tool do what when, so Gulp is my go to.
I happened to maintain old projects that I did some months ago, and going from Gulp 3 to 4 was a breeze.
I think in the end if you try to go progressive, and test everything like a psycopath even if you just add this tiny little package you might be able to locate the source of the issue earlier, but I generally have the feeling like you that build tools have made our lives more complicated (mostly if you are not a full front-end developer that does other things like keeping up with all those build tools releases and features).
I'm actually also refactoring our old Gulp projects to Webpack because they have become completely outdated and only throw errors.
Instead of debugging the whole thing I just update it to the latest and greatest.
The biggest cause is updating the node and npm versions on my machine of course.
So in a way it's my own fault.
Maybe this is why agencies often have their own virtual machine where they control versioning for all developers instead of lettings the developers update it whenever they want.