Ensure classes defined in Nuxt config are imported

[pedantic-git]

🔗 Linked issue

Resolves #1011

❓ 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

As discussed with @ineshbose in #1011, moving to the new directory structure of Nuxt 4 causes the two class keys in nuxt.config.ts to no longer be caught by Tailwind. This PR puts them back using the inline() keyword.

Note that it also had to move JSON.stringify higher up in the code, since these need stringifying inside the keyword. This shouldn't cause any issues because the variable is private and only used once.

Happy to make any changes requested!

[netlify]

👷 Deploy request for nuxt-tailwindcss pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	197921d

[what-the-diff]

PR Summary

• Refinement of importCSS function
  The importCSS function has been updated for better usability. It now turns the directory paths of source files into strings when compiling these files. This simplifies the process of accessing and managing source files.

• Expanding the parsing parameters
  We've added new variables to the sources array for parsing from the Nuxt configuration. This particularly affects htmlAttrs.class and bodyAttrs.class, providing greater control and flexibility in parsing these classes.

• Enabling Inline Source Definitions
  The PR includes an enhancement that lets developers define source definitions inline. This is based on the configuration values if any are present.

• Refactoring of getContents Method
  The getContents method, used for generating sources in CSS, has undergone modifications. We've removed the JSON.stringify operation from source values. This makes the process more streamlined, increasing efficiency and simplicity.

[ineshbose]

sorry it took me a while, I was thinking about this hook as passing JSON.stringified strings here would have severe effects. Let me think of some ideas and apply onto this PR

[pedantic-git]

I understand! But worth noting that I didn't add this call to JSON.stringify: it was already in the codebase and I moved it.

I had to move it here so that only the bit between () was stringified rather than the whole string.