docs: mention tailwindcss-cli if tailwindcss init fails

[devbyray]

Updated the init commands because the other one doesn't work. Found this solution here: https://www.devgem.io/posts/why-npx-tailwindcss-init-fails-and-how-to-fix-it

🔗 Linked issue

Not that I could find.

❓ 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)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I have updated the documentation for the init command. The current one online doesn't work, so I found a solution on https://www.devgem.io/posts/why-npx-tailwindcss-init-fails-and-how-to-fix-it

So I thought let's update this for everyone 👍

If my title is not correct, or if I need to change something, please let me know 😉

[netlify]

❌ Deploy Preview for nuxt-tailwindcss failed. Why did it fail? →

Name	Link
🔨 Latest commit	a682d1f
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-tailwindcss/deploys/679357505de7860008e660e9

[what-the-diff]

PR Summary

• Update of Installation Instructions
  The commands previously listed in our installation instructions have been updated to reference the latest version of the Tailwind CSS Command Line Interface (CLI) for Node Package Manager (npm), yarn, and pnpm. This update ensures that users will initialize the newest version of the program during setup. Please see the specific changes below:
  • Instead of using npx tailwindcss init, we now recommend npx tailwindcss-cli@latest init.
  • Instead of using yarn tailwindcss init, we now recommend yarn tailwindcss-cli@latest init.
  • Instead of using pnpm dlx tailwindcss init, we now recommend pnpm dlx tailwindcss-cli@latest init.

[ineshbose]

Looks good - thank you!