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
848 stars 49 forks source link

Differentiating between multi-entry and multi-pages #324

Closed jakearchibald closed 4 years ago

jakearchibald commented 4 years ago

Fixes #274

jakearchibald commented 4 years ago

The diff here is bad. Once the build is complete, I'll come up with a better way to review this.

github-actions[bot] commented 4 years ago

🚀 Deploy preview for 41ee0df: https://tooling-report--6b6e48a1135694d6.web.app (Fri, 26 Jun 2020 15:46:03 GMT)

firebase-preview-action

jakearchibald commented 4 years ago

https://bundlers.tooling.report/code-splitting/multi-entry/ is now https://tooling-report--6b6e48a1135694d6.web.app/code-splitting/multi-pages/

I've adjusted the description, and I've changed the webpack test to use the HTML plugin. I used the HTML plugin since it seems to be the documented way in their guides, whereas runtimeChunk doesn't really seem well documented in webpack land.

https://bundlers.tooling.report/code-splitting/shared-objects-between-entry-points/ is now https://tooling-report--6b6e48a1135694d6.web.app/code-splitting/multi-entry/

Again I adjusted the description, and the webpack description a little.

jakearchibald commented 4 years ago

I also reinstated the multiple-references test from https://github.com/GoogleChromeLabs/tooling.report/pull/323. Since git has confused the renames, it was easier to re-make that change here, rather than comb through a ton of incorrect conflicts.

developit commented 4 years ago

Mostly nits, otherwise LGTM.

jakearchibald commented 4 years ago

Merged manually because GitHub is being crap