[thelarkinn]

We strive to be as backwards compatible as possible. But we also hold ourselves accountable to keeping pace with the ecosystem.

Most breaking changes are to accommodate the number one ask of our users: faster, smaller builds.

We asked what the time frame they wanted for releases. We got out of a couple thousand responses 6mo being the sweet spot. Appreciate the candid feedback though.

In regards to the v1 docs: we wanted to have a fresh start. I don't imagine our docs pages now changing for awhile. Each major breaking change we ship a migration guide so that people can upgrade.

[skrebbel]

Sean, you don't know this but for quite a while now I've been amazed about your work responding to everybody complaining about Webpack on the internet, anywhere. There's absolutely no requirement for you to be so nice to users and yet, here you are again. Hats off, you're making the world a little bit prettier.

This time I'm the one complaining, and I must admit that I'm curious about the exact wording of that question about release time frames. If you asked "how often do you want to make config changes just so you can update Webpack to the latest version", I bet many people would answer "never" instead of "6 months" :-)

But hey, we established that we have different ideas about what the compat sweet spot is and you and yours are the one doing all the selfless work and I'm the guy complaining on the internet, so take everything I say with a bag of salt.

All that said, any chance you could make a teeny tiny little link from the Webpack 1 "THESE DOCS ARE GONE" pages to http://devdocs.io/webpack~1/ or some place like that? There are people who inherit old codebases and it would be very nice for them to not _have_ to update Webpack just to find answers to their problems.

[bsimpson]

When I first started using Webpack 4 years ago, it had the most finnicky, difficult-to-configure (perhaps even magic) API I can think of. It worked really well once you got it configured, and wSokra was incredibly helpful and supportive in the chat room; but if you didn't have a known-working config and/or access to wSokra, well, good luck.

I'm highly supportive to anything they can do to make it easier to configure and maintain, even if the cost is breaking the old APIs and making folks migrate to newer ones.

Hopefully as someone works on a library and learns a problem space more thoroughly, they have better knowledge of what an ideal API would look like. I know migration can be painful, but I'm very supportive of long-run improvements to a project.

[thelarkinn]

Ah yes so we removed the page but is all still under our WIKI on webpack/webpack. Mind submitting an issue and we could surface a little note on our README?

[skrebbel]

Done, thanks!

[oneweekwonder]

> In regards to the v1 docs: we wanted to have a fresh start.

Those who inherit a old codebase normally don't have the luxury to start fresh, or sometimes even upgrade. The work and effort you put into webpack is selfless; which is great; and you should be thanked by users! Removing the v1 docs was selfish, and unfortunate.

[luikore]

I also switched to parcel-bundler for a fresh start.