search

GoogleChromeLabs / tooling.report

tooling.report a quick way to determine the best build tool for your next web project, or if tooling migration is worth it, or how to adopt a tool's best practice into your existing configuration and code base.
https://tooling.report
Apache License 2.0
847 stars 49 forks source link

Update outdated content #399

Closed chenxsan closed 3 years ago

chenxsan commented 3 years ago

It's documented in code splitting guide now https://webpack.js.org/guides/code-splitting/#entry-dependencies:

image

sokra commented 3 years ago

The fix is also included in https://github.com/GoogleChromeLabs/tooling.report/pull/395

surma commented 3 years ago

tooling.report is currently targeting Webpack v4 — the documentation you link to is Webpack v5 which we will hopefully land soon-ish via #395.

Closing this in favor of that PR.