Most recently, web.dev launched a site called (Tooling.Report)[Bundllers.tooling.Report /], which was a quick way to determine the best build tool for the next Web project, or whether tool migration was worthwhile, Or how to apply the tool’s best practices to your existing configuration and code base.
- This site shows a summary of the results of the custom build tool test suite.
- Build tool tests are configuration files created specifically to handle functionality.
- It is discussed through 48 functional tests
Test cases and pass rates
So far, the latest parcel V2 has scored the highest
Use cases
State that
Results the detail
conclusion
The test results show that the Parcel V2 stable is ready to build in a production environment, and the internal test summarizes a few points from the field
- Parcel Code Splitting performed better than Vite’s Library mode
- This is mainly reflected in the case of multiple dependencies such as Web worker
- Be smarter about dependency analysis
- Automatic DTS is more user-friendly
- Package management automatically solves business problems
*The defect is package management effectiveness in the case of PNPM workspace
stretch
The subsequent functional extensions of Parcel V2 are all extended through the Plugin System as follows:
Those interested can stay tuned to see what happens next to Parcel
The author
Ken