Feedbacks and Ideas

[pi0]

Note

Update: I'm no longer working on this.

While the new CLI is still in the early stages, if you have any feedback about experience or ideas, it is more than welcome here to discuss!

---

Related topics:

• Project Vision
• The journey of Nuxt CLI Generations

[HigherOrderLogic]

In a Nuxt project, we have the module system which let users make changes to routes, middlewares, components, ... So is it possible to make a similar module system for the CLI so that users can customize it, ex: add more commands, overwrite behaviour, ...?

[pi0]

Definitely. Making CLI (commands) extendable is one of the goals. I think we can also think about some ideas about CLI extensions that act as middleware and hook into other comments. Feel free to make an issue in unjs/citty as well to follow up with some ideas 👍🏼

[cayter]

Is this still being planned? I just found out about Nuxt ecosystem and is mindblown by the great quality of how things are so well thought out to provide a full stack framework that works with modern frontend UI library. My use case for the custom command is for me to add db:migrate, db:seed commands.

[pi0]

@cayter That one is also certainly considered as well (expect it really soon!). You can track from https://github.com/unjs/nitro where we initially make the bases.

[Youhan]

👀

[Celibioux]

Really amazing work as always ^^ just one question please ! there will be an auto git init for new project scaffolding like in Nuxt 2 if i recall right ?

[pi0]

That would be a nice idea! Would you please open an issue to track the feature request? 🙏🏼

[unpseudocomplique]

Nuxt is a FullStack framework, so i dream of a cli that boost productivity while building apps.

I remember at school we worked with Syphony and if i remember well we used composer. With it, we were able to generate model and route, for exemple:

I'm creating the model User

nuxi model user
-- created model user
enter you fields or empty to finish
firstname
---enter your type
string
--next field
lastname

type enter on empty

-- model created with fields firstname, lastname
-- generated get, post, put, delete

And route will be generated automaticly. This would be so much (useless) code to not write 😯

This setup would be quite opinionated, but would be so cool to use daily.
Latter this could go further with relationships, maybe prisma or drizzle can provide tools to add relationships to the models and make it work with nuxi ?

To sumup i would love to create / update models and automaticly create corresponding routes

(found a small exemple)

[pi0]

Hi, dear @unpseudocomplique. Thanks for putting the feedback. As a former symphony user i also always felt this feature is missing. FYI, currently we have basic nuxi add <template> feature that can create these simple opinionated templates:

We plan to enhance this feature with an expandable templating/scaffolding engine. You can track the progress in #58 👍🏼

[unpseudocomplique]

Nice :D ! I don't see any mention about backend / data model, hope one day this could be part of the cli!

[rrd108]

I was thinking today to make a nuxt module for this, using prisma. I mainly interested in creating api endpoints and corresponding pages / components.

But I saw this discussion so I thought, maybe you would need some help here.

Something like this? rrd108@13f28af

[Celibioux]

Hello Nuxters ! a question please for the CLI as Bun came to play a nice role wouldn't be nice to have a choice in the CLI about the desired runtime ? Bun or Node :)
And one more thing if someone could please correct me ...when using Bun ...do we really need .npmrc ?
Thanks you for your time reading this

[HigherOrderLogic]

I don't think support for Bun is needed, at least for now. It's not a "drop-in replacement" as they have advertised yet, too immature for Nuxt to run on.

[Celibioux]

But Nuxt already support and run on bun runtime with --bun flag ( to force the Bun runtime instead of Node no ?

[Celibioux]

and it's not a drop-in replacement for sure ! but a choice !!

[Celibioux]

Thank you for much for your hard & great work as always Mr @pi0 🥇 the last release is really fabulous ^^ it gives the joy of making many more new projects XD
and that i mentionned new project ...i've noticed a small thing a while ago but...when we scaffold a new project like npx nuxi@latest init great-nuxt-project for example ....in the package.json name : nuxt-app and it's on the modules too ! is it the desired behavior ?

[pi0]

Thanks for the kind words. Yes it is a current limitation. We the progressive scaffolding framework coming, we can do much more things like this to update package.json:name and README.md based on provided options.

[noook]

Kind of related to this feedback regarding commands to generate file in a Symfony way, I would like to suggest having the possibility to run commands, or scripts within a project.

In Symfony we have Console Commands and they are very useful when you need to write small scripts that you don't want or don't need to expose through an endpoint to run it. But instead, you can run it as a command and benefit from all the ecosystem around it (Dependency injection, runtime configuration etc...).

An example of a usecase would be when you need to create credentials for an external API (let's say, Google APIs) you need to generate a token for your web application, and you usually only need to run it once, and I believe this could be easily achievable as a command.

I imagine something like nuxi run google:auth and then it would run the authentication flow for the app

[pi0]

Yes! Such commands (to be similar to symfony/laravel), require runtime integration (otherwise we need to duplicate code logic for example for auth or db integration).

With upcoming "Nitro Tasks" feature, this would be possible for Nuxt!

[noook]

Looking forward to it ! You guys are already thinking 3 steps ahead 💚

[rohrig]

Hi @pi0 👋 , I'm super excited about Nitro Tasks after seeing your talk. I'd love to follow and even help out if possible. I was putting my free time energy into upgrading nuxt-scheduler but this will render that obsolete. So, I'd rather spend that energy here. I'd love to help. Where can I follow the planning/progress?

[bitsnaps]

I really like to init Nuxt with a specific version instead of @latest by default, right?

[pi0]

Hmm it is possible and might be useful for particularly making reproductions 🤔 But do you have more usecases for this?

[bitsnaps]

Specifying a Nuxt version provides reproducibility, easier debugging, and control over the environment. It ensures consistency across collaborators (specially with large codebase/multiple versions and deployments env Deno/Bun...) and simplifies tracking down bugs by isolating the issue to a specific version, also periodic reviews to update the version gain bug fixes and security patches while maintaining stability are the most reasons IMO.

[pi0]

Surely that would make templates more predictable but it is really job of the lockfile to ensure not only Nuxt but many of its sub-dependencies that sometimes can make regressions determined. For that you can internally make a template with nuxi init -t gh:org/name that contains lockfile.

Anyway, don't get me wrong i think it is a nice idea to support this flag to be able make nuxt reproductions with a specific version of it (only it will lock nuxt core nothing else)

[arashsheyda]

the --host flag is great! but one downside of it is that we have to add the host to hosts file manually. would be realistic and a good idea to ask user if they want to add it?

[pi0]

Feel free to initiate a discussion in listhen repo would be glad to explain more and give some ideas.

[they-cloned-me]

Hi everyone 👋🏿 ,

Regarding the add command, I find it weird that we have this format for pages, components etc

# “add” comes before plugin, component etc
npx nuxi add {plugin, component, composable, layout, page, middleware, api}

But in the case of modules, we have to do:

# module comes before add 🫤
npx nuxi module add <NAME>

Wouldn’t it be better to follow one format for all?
What is the reasoning behind this difference?

Edit:
Just to be clear, I understand the nuxi module... command has other functionalities like search, but I still think it’s worth it grouping similar actions.