Deprecate renderviz?

Well comparing both I still think this module is very helpful as it - as the module name says - visualizes the results, while the core
renderer.config.debug: true simply adds HTML comments.

So I'd vote to keep this! :)

Could we at least link https://www.drupal.org/node/3162480 → and https://www.drupal.org/project/cache_review → from the project page in the meantime?

Confirmed this is much lire convenient than comments in markup as comments are mostly useful to check what exists around a given element, while Renderviz allows discovering all that exists in a page, to pinpoint what is bringing a specific tag, context, or max-age.

Hi,

@dpi, links added to the project page.

So we need to determine if it would be possible to use Core render cache output and only keep the JS for visualization?

That way we will avoid the bug from #2847712: Broken markup →

Then should the module be reworked to use Core cache debug output and only focus on visualization or the data exposed by the module are more precised than core ones?