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.
So there are comprehensive information on each page and each build tool.
for example this page: https://bundlers.tooling.report/non-js-resources/html/preload-assets/
The only issue which maybe gonna be misleading and seems critical for making a decision by developers is which version offers these feature that has been mentioned.
For example, the latest version of the webpack (version 5 when I'm reporting this issue) does not support either of preload-webpack-plugin and resource-hints-webpack-plugin since they are outdated.
It would be nice if we can focus only on the latest version of bundlers or the one which maybe the next best choice for starting a new project.
What are your thoughts?
So there are comprehensive information on each page and each build tool. for example this page: https://bundlers.tooling.report/non-js-resources/html/preload-assets/ The only issue which maybe gonna be misleading and seems critical for making a decision by developers is which version offers these feature that has been mentioned. For example, the latest version of the webpack (version 5 when I'm reporting this issue) does not support either of
preload-webpack-pluginandresource-hints-webpack-pluginsince they are outdated. It would be nice if we can focus only on the latest version of bundlers or the one which maybe the next best choice for starting a new project. What are your thoughts?