-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(subcommand): add subcommand support #644
Conversation
Bundle StatsHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded
Removed
Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Open in Stackblitz β’ nuxt-cli-playground
commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
other than comment LGTM.
My main hope in new nuxi with external commands was to avoid executing another process but import citty-compatible modules as command and be able to pass more runtime info but seems far reach today.
oh, that would be nice. I think we can refactor to that as soon as supported. maybe expose a JSON with metadata? |
π Linked issue
β Type of change
π Description
resolves #62
This adds arbitrary CLI subcommand support to
nuxi
. (For example,@nuxt/module-builder
exposes anuxt-module-build
command, which is outdated, as nuxt/module-builder#356 points out.)