Enhance the experience of create script

[daalfox]

Now that we are at 2.0, let's improve the experience of create script. I am willing to help move it to Rust maybe?

I always get frustrated about not being able to get a combination of the templates and needing to update packages to latest version. Let's make it so that we select what we need as multi selections, always install the latest versions and structure the final project after we determined what packages will be in the initial state.

[Tommypop2]

Hey! Thanks for the issue.

This has been a feature I've wanted to implement for a while (and one we used to have in the past). I'll get round to an implementation soon but just trying to get it right.

Using the latest versions of packages would be great but sometimes things break in minor (or even patch!) versions and we don't want that to break project scaffolding for everyone.
The other question is where to store the configs for scaffolding these new dependencies (we used to call them "integrations")? They used to be in the CLI but I'm now moving towards the idea of placing them in the templates repo so we can have CI update the dependencies and test everything.

As for Rust, it did actually used to be in the CLI but I found it wasnt a great fit as it'd mean native binaries for a rust CLI so we'd need to compile artifacts for every conceivable platform and architecture. A Javascript CLI is almost much smaller and more than performant enough for this I think. Though more than happy to reassess this if there's a nice way of making Rust work that would improve UX

[daalfox]

Using the latest versions of packages would be great but sometimes things break in minor (or even patch!) versions and we don't want that to break project scaffolding for everyone.

I think that's the exception rather than norm and it is easy to downgrade anyways and there is no need to update dependencies every time if it works.

The rust argument is fair and I am looking for solutions too.

In my opinion the cli should just construct the installation command based on user selections and lock only major versions such as tailwindcss@4 and so on. Then perform the configuration after package.json is formed

[daalfox]

I'm curious to see your new implementation first now that you are close to something that works. I will explore different approaches too