What is tooling.report?

It's 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.

Brought to you byweb.dev

Getting Started

This homepage shows the aggregated results from a bespoke suite of build tool tests. A build tool test is a configuration file created to specifically handle a feature. We intend for the capability results and the configuration files to be transparent; to encourage learning & growing together.

Yes, each of the 61 feature tests have a hand written config file! We worked with the build tool authors to ensure fair tests and succinct configuration. It's all in Github.

We highly encourage you to contribute too!

#Summary

  • browserify

    56%
    34.5/61
    Tests Passed
  • parcel

    47%
    29/61
    Tests Passed
  • rollup

    65%
    40/61
    Tests Passed
  • webpack

    62%
    38/61
    Tests Passed

Information

Below you'll get to see how your favorite, or new to be favorite, tool is handling our industry best practice test suite.

Each tool scores as follows:

Legend

Pass
Partial Pass
Fail

The Tools

We chose browserify, parcel, rollup & webpack first out of popularity; to cover the most surface area. We are actively aggregating feedback for the next set of tools and tests.

browserify logo
browserify
parcel logo
parcel
rollup logo
rollup
webpack logo
webpack

#Code splitting

#Hashing

#Importing modules

#Non-JavaScript resources

#Output module formats

#Transformations

Plant with tall leafs and vines in a pot

Questions or Concerns?

We want to hear from you, let us know how to make this better. Open up a Github issue and we’ll track it there. Thanks!

Open a Github Issue