I'm currently upgrading a repo that is maintained internally and uses grunt+webpack+karma+jasmine and I strongly agree with this comment. The tool has been runn

I'm currently upgrading a repo that is maintained internally and uses grunt+webpack+karma+jasmine and I strongly agree with this comment. The tool has been running webpack 1 and it works but now that webpack 1 docs have been removed we want to upgrade to webpack 2. It's been a host of issues, with the API changes being the least of it. webpack 2 introduced ES6 syntax in their plugins which grunt mangles when passed to its config https://github.com/gruntjs/grunt/issues/1595 https://github.com/gruntjs/grunt/issues/1595. Admittedly that's a grunt issue but seeing how many teams use this tool and have already configured their applications to build via Gruntfiles we can't move things overnight. I had issues with loaders (now rules) running at the appropriate time for istanbul as well and had to go through two or three now-defunct packages and piece together how to make it work with our rather unique setup. Honestly in this adventure I think our issue is grunt and the underlying bespoke hacks people have designed over the years, but in Enterprise this just keeps me from being out of a job.