fix: remove nuxi dependency and prompt to install when needed

[wattanx]

🔗 Linked issue

Fixes: #900

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

In nuxt/cli, nuxt is set for bin field.
This may conflict with the nuxt command in nuxt 2.
https://github.com/nuxt/cli/blob/master/package.json#L13-L17

So, I'll change to install nuxi when you want to use nitro.

The following code was used as a reference.
https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/core/features.ts

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[danielroe]

This looks good to me ❤️

[pi0]

You can directly use consola.prompt (or logger.prompt -- not tested) to avoid new dependency

[pi0]

This looks another good idea but i believe safer approach might be supporting nuxt2 binary directly from nuxt@2 dist as a non conflicting feature. This looks more like a workaround to me.

Also, do we want to keep supporting nuxi for bridge? (we might potentially drop it in next nuxi major version).

[danielroe]

@pi0 Do you mean that users of Bridge would have to change the cli command in their package.json scripts to nuxt2, if they are not using nitro?

[pi0]

I am suggesting adding an additional (nonconflicting) nuxt2 command so that the bridge can more safely enable nuxi by default.

[danielroe]

Sounds good to me. @wattanx are you happy (keeping all that this PR does) to also add a nuxt2 legacy command?

[wattanx]

Yes, I'll add it!

[danielroe]

We should probably also update the docs too for the bridge migration.