Practically no software can be developed without frameworks, libraries and "tools". This is one of the reasons for the triumph of open source, because software projects are almost always and to a large extent based on existing code. The better these can be viewed, understood and, above all, adapted, the more suitable they are for developers to use in their projects.
If you were already surprised by the 115 languages in the previous section (link), hold on tight. Frameworks and libraries exist in the thousands. If "only" 220 were mentioned here, it is probably because the study participants did not want to list everything that is still used somewhere as a dependency in a project. (A library or a framework is also often referred to as a dependency.) It can also be controversially discussed what is now most likely a framework, a library or a tool.The boundaries are not clear and many projects move more or less in all areas.
Nevertheless, the right choice of framework is just as relevant for the success of a solution and the satisfaction of the developers as it is for the programming languages. By choosing the right framework, sometimes even a less popular language can be upgraded and the work becomes fun again. Conversely, a tedious framework or an exhausting library can destroy any fun in a language.
In general, the comparability here is less strong than with programming languages, since the frameworks, libraries and tools can come from very different areas and are not always interchangeable.