maintenance chore - replace Cliffy

[cscheid]

Cliffy has been a constant source of toil and churn in our codebase, and I'd like to not have to deal with it anymore.

[winniehell]

@cscheid in #10809 (comment) you commented that this issue will happen in 1.7 but here is no milestone assigned.

do you already have plans what to use instead?

[mcanouil]

Milestones are for internal management and does not represent roadmap or promises on what will be done or not in a release.

Thank you for your interest but please avoid pinging developers especially asking things about status.
As you can see, they do update issues when they think there is something worth mentioning to themselves or users.

[winniehell]

sorry, my intention wasn't to ask about status but to offer help. if no previous research for alternative (outside of this issue) has happened, I would do it myself and post the result here.

[winniehell]

Milestones are for internal management and does not represent roadmap or promises on what will be done or not in a release.

I understand but I interpreted the linked comment that not adding a milestone here was just an oversight. no intention to enforce any deadline, just trying to help fix a potential inconsistency in the internal planning.

[cscheid]

When we have communications that we're ready to share with the public, we do that in the comments.

[winniehell]

I would make an attempt to replace Cliffy with https://www.npmjs.com/package/clipanion in the hope that it works with Deno (haven't tested yet).

EDIT: tested, works ✅

I've started the migration: main...winniehell:quarto-cli:cliffy-to-clipanion

[winniehell]

currently I focus on the argument / command parsing which is the biggest chunk of cliffy.

for prompts I intend to use https://www.npmjs.com/package/enquirer

for tables I intend to use https://www.npmjs.com/package/cli-table3

[winniehell]

I finished the first part: #11325

…but overlooked that npm imports are not supported by deno bundle: #4955