check_urls default output is too convoluted

[iacore]

Version

https://cdn.jsdelivr.net/gh/lumeland/lume@3.1.1/

What steps will reproduce the bug?

Compare these two:

https://cdn.jsdelivr.net/gh/lumeland/lume@3.1.1/plugins/check_urls.ts
https://deno.land/x/lume@v2.5.3/plugins/check_urls.ts

What is the expected behavior? (@v2.5.3)

See broken links printed out in terminal

What do you see instead? (3.1.1)

"Warning: 4 warning print in console".

Too vague. Much better to print the links instead.

Additional information

No response

[oscarotero]

This was aligned with other plugins like seo or validate_html. The report was moved to the debug bar because the console is not very practical for long reports.

[iacore]

i still think it should print in the console. i'm used to working with UNIX files.

Still don't see a point of debug bar. Definitely should be able to route all debug bar output to console.

The [broken link] emoji looks quite cool.

Terminals may support OSC 133. It's very convenient to press a key combination to only show the latest command output. Lume can use that as well.

[oscarotero]

I guess it can show at least the first broken links (with a limit of 50, for example), but when you're building a long site, it can show hundreds or even thousands of links and it's unusable, specially if the output is mixed with other outputs that Lume generates, like the list of files saved in _site or reports from other plugins (let's say you have validate_html and check_urls plugins running in the same build). This is also incompatible with other customizations like LUME_LOGS that some people use to have a quiet mode. And since you can use a function to customize the output, I considered that it's better to use by default the debug bar. Can I ask why you don't like it?

---

Previous versions of Lume didn't work like a terminal because it was executed as echo "..." | deno run -A - to use the import map (see this)

Lume 3.1 changed this since Deno can now run deno run -A lume/cli.ts and it's correctly resolved, so I guess it's possible to have some interactivity here. I'm not an expert of this, but if you have any idea and want to contribute, you're welcome.

[iacore]

Can I ask why you don't like it?

More clicks. When it's in terminal, I see the output immediately.

For interactivity design, the user can send USR1 (or SIGINT with Ctrl+C) to get a REPL.