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.
[x] test pages (detail of test with each tool results)
[ ] tool pages (view results for 1 tool at a time, not compared to others)
We've got the data, we've got components (cards and datagrids), so this may be low effort with great results. Means we'd absorb all links to like webpack and rollup to this page, and then on this page link out to the respective tool. Thoughts?
Our current IA:
We've got the data, we've got components (cards and datagrids), so this may be low effort with great results. Means we'd absorb all links to like webpack and rollup to this page, and then on this page link out to the respective tool. Thoughts?
This is a good one to be designed in the browser.