Add "tailwindcss@next" to the "peerDependencies" section in the package.json file.

[suiyueou]

Description

Before using nuxt ui, I briefly skimmed through the repository and found an already closed issue: 3018

The error and solution mentioned in this issue (the v2 documentation indeed did not mention the solution) can actually be resolved by adding tailwindcss@next to the peerDependencies section in the package.json file.

This is because when nuxi module add installs a module, it not only installs the module itself but also scans the module package's peerDependencies.

For example, when using nuxi module add pinia, since @pinia/nuxt has pinia listed in its peerDependencies in the package.json, both @pinia/nuxt and pinia will be automatically installed during the module installation.

If there are dependencies in peerDependencies that you do not want nuxi module to install automatically, you can use peerDependenciesMeta to ignore them, for example:

"peerDependenciesMeta": {
    "pinia": {
      "optional": true
    }
  },

Therefore, Nuxt UI can specify tailwindcss@next in the peerDependencies of package.json, ensuring Tailwind CSS is automatically installed when the Nuxt UI module is installed.

This solution applies to both v3 and v2.

PS: I noticed typescript in the peerDependencies of the v3 package.json. Is this a necessary dependency similar to tailwindcss? If not, after adding tailwindcss, perhaps peerDependenciesMeta could be used to ignore it.

[benjamincanac]

I'm a bit confused, is this an issue for v2 or v3? 🤔 I don't think it's necessary to add tailwindcss to the peerDependencies as it's already in dependencies: https://github.com/nuxt/ui/blob/v3/package.json#L118

[suiyueou]

Hmm....

For pnpm, when using nuxi module add ui to install nuxt ui, this should work equally well for both v2 (the current latest version) and v3 (the future latest version).

Adding tailwindcss to peerDependencies is simply to ensure that when using nuxi module add ui, nuxi module add can automatically install both the module itself @nuxt/ui and the necessary dependency tailwindcss listed in peerDependencies for the user.

Of course, if installing via pnpm add @nuxt/ui, you still need to manually install tailwindcss as documented.

This does not conflict with the existence of dependencies in package.json.

For example, in the package.json of @pinia/nuxt, pinia exists in both devDependencies and peerDependencies.

[benjamincanac]

@suiyueou I've made the PR but I'm a little concerned, this will happen even when the user has shamefully-hoist=true which we don't want to 🤔

[suiyueou]

Thank you for your adoption. Perhaps this requires more discussion and time to verify.

Wishing you a pleasant life.