webpack.js.org

Look no further than Webpack shutting down their website and documentation then angrily dismissing POCs who are concerned they can't do their jobs. [1] In the same light, they shut down all of the incredibly respectful criticism they received, mostly centered around not having the website accessible after dismissing the message. [2] [1] https://github.com/webpack/webpack.js.org/issues/3765 [2] https://github.com/webpack/webpack.js.org/issues/3762 Have we reached a point where open source will throw POC developers under the bus in order to score political virtue points? It's a total trainwreck, and politics is used as a weapon in open source against political enemies through shut downs, egregious code of conduct policies and arbitrary enforcement actions.

Have a look at this issue [0], I think it covers most of the docs for v4. [0] https://github.com/webpack/webpack.js.org/issues/1861

There's a big webpack 4 documentation update PR in the pipeline: https://github.com/webpack/webpack.js.org/pull/1856

They have [0][1] ("beta" was dropped from the v4 releases at v4.0.0), and are actually in the process of updating the documentation [2]. It's just odd to do that after a release. [0] https://www.npmjs.com/package/webpack [1] https://github.com/webpack/webpack/releases [2] https://github.com/webpack/webpack.js.org/pull/1905

Coming from a no-design-ux background, I never considered this and it would be a perfect issue on our github. Would you be interested in creating it? github.com/webpack/webpack.js.org/issues/new

Coming from a no-design-ux background, I never considered this and it would be a perfect issue on our github. Would you be interested in creating it? github.com/webpack/webpack.js.org/issues/new

Thanks for the thoughtful reply. I've created an issue for it so that we can discuss and plan where and what content should be added. https://github.com/webpack/webpack.js.org/issues/416 Also, if you would like to be involved in the discussion or thread, feel free to. We welcome constructive ideas and suggestions.

DISCLAIMER: (dupe comment) This was an alpha feature that got leaked that we didn't expect to be circulated. Therefore we don't have UX/UI yet. We would love help and support so PR's, suggestions, issues are all welcome on github.com/webpack/webpack.js.org

Hey!!! This was an alpha feature that got leaked that we didn't expect to be circulated. Therefore we don't have UX/UI yet. We would love help and support so PR's, suggestions, issues are all welcome on github.com/webpack/webpack.js.org

Can you please add some documentation for sourcemap and debugging to the doc? WP 1's sourcemap doc is confusing as hell and WP 2's doc just copied that over. I imagine debugging un-transpiled code with sourcemap is one of the most common use-cases. And I'm not alone if you look at the disqus of WP's doc[0] and a blog by @bebraw[1], one of the guys running webpack.js.org. I even opened an issue[2], I hope it can make into your MVP. [0]: http://survivejs.com/webpack/developing-with-webpack/enablin... [1]: https://webpack.github.io/docs/configuration.html [2]: https://github.com/webpack/webpack.js.org/issues/273

I can understand your concerns but we made a promise early on that we wouldnt release v2 from beta until our MVP docs milestone is complete. We are just around 90% completion (http://github.com/webpack/webpack.js.org/milestone/1) After that we will release v2. Help always wanted! <3