Skip to content

Conversation

@selemondev
Copy link
Contributor

This pull request is intended to update the configuration page in the Nuxt Tailwind documentation with the latest configurations to get rid of the deprecation warnings shown below:

nuxt-tailwind

@what-the-diff
Copy link

what-the-diff bot commented Mar 23, 2024

PR Summary

  • Update to tailwindcss Configuration Path
    The cssPath in the tailwindcss configuration has been updated. It now includes an additional option injectPosition, which allows for more flexibility in the positioning of css.

  • Enhanced Exposure Level Control
    The exposeConfig property has been adjusted to contain a level property. This allows for greater control over how exposed our configuration is. Note that the exposeLevel property has consequently been removed from the tailwindcss configuration.

  • Removal of Redundant Properties
    The injectPosition property has been removed from tailwindcss configuration. This keeps the codebase cleaner and more efficient, avoiding unnecessary redundancy.

  • Simplification of the Config Path
    We've simplified the configPath property. It's now just tailwind.config, which is much easier to understand and manage.

  • Default Configuration Update
    The default config property has been updated to an empty object. This ensures that our configuration starts from a clean state, mitigating chances of unwanted behaviors.

  • Enabled Viewer By Default
    By default, the viewer property is now set to `true'. This ensures that all developers can view the tailwindcss configuration without having to change any settings.

@ineshbose ineshbose merged commit 11c980a into nuxt-modules:main Mar 23, 2024
@ineshbose
Copy link
Collaborator

Nice spot, thanks! ❤️

@netlify
Copy link

netlify bot commented Mar 27, 2024

‼️ Deploy request for nuxt-tailwindcss rejected.

Name Link
🔨 Latest commit 13fe501

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants