Sindre Sorhus

Yes, we show the error in the Alfy itself instead: https://github.com/sindresorhus/alfy/blob/0dafe8f4f1b8e9b95b4d017a47dfe7d1553b0dbe/index.js#L70-L96 But you're right, we should also enable `stderr` to go through so it's also shown in the debugger.

If anyone wants to work on this, see the initial attempt and feedback in https://github.com/sindresorhus/alfy/pull/112.

Yeah, it could. We could document that option. I don't plan to move to discussions myself in the near future as it's too much work to manually move individual issues....

I'm planning to write a blog post about this when I have some time. Reopening so I don't forget.

@azz The next XO version will come with Prettier built-in: https://github.com/sindresorhus/xo/commit/fd89175682810fe2a4ec8d10c3f3104d31ed37f1 :)

I don't see how that matters in this case as it's for Node.js, not browsers.

I'm neutral about it. Many of the exports have too general names when imported without the namespace though. `ansiEscapes.image()` makes it clear what it is, but `image()` could be anything.

@Qix- It's not just `image()`. It applies to most of the exports.

There is some useful info in https://github.com/watchexec/clearscreen/blob/main/src/lib.rs

https://stackoverflow.com/questions/8343250/how-can-i-get-position-of-cursor-in-terminal We should indeed document this better.