Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Extending citty using user commands

Open
#151 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
cli

Research direction

Start by reviewing the linked Nuxt CLI discussion and the citty project context around commands implemented by users and module authors. Define the desired extension scope and integration expectations for projects such as NuxtHub CLI, including whether ORM integrations are supported; done means the feature requirements and implementation path are agreed.

Written by the indexing model from the issue text.

Description

enhancement
Describe the feature

Hey 👋,

I read this: https://github.com/nuxt/cli/discussions/3#:~:text=%F0%9F%A7%A9%20Modular,single%20core%20implementation. and you're talking about "commands can be implemented by users, module authors, core, and also ad-hoc modules".

Adding the ability to extends commands by some provided by users could be very useful for a lot of projects and could avoid to rewrite a new CLI all the time. For example, adding capability to the NuxtHub CLI could help a lot to provide better integrations with ORM. Even the NuxtHub CLI could be part of Nuxt CLI.

Is it still something you're working on? Is it still something needed or wanted and if yes, do you thing we could start working on it?

Additional information
  • Would you be willing to help implement this feature?
Dominant language
TypeScript
Stars
1.3k
Forks
63
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from unjs/citty

All issues in unjs/citty

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.