Skip to content

feat: add initial tw4 support in v6 #980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

feat: add initial tw4 support in v6 #980

wants to merge 3 commits into from

Conversation

ineshbose
Copy link
Collaborator

πŸ”— Linked issue

❓ 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

Copy link

netlify bot commented Apr 9, 2025

βœ… Deploy Preview for nuxt-tailwindcss ready!

Name Link
πŸ”¨ Latest commit 905cda4
πŸ” Latest deploy log https://app.netlify.com/sites/nuxt-tailwindcss/deploys/680570592b8deb00071d4637
😎 Deploy Preview https://deploy-preview-980--nuxt-tailwindcss.netlify.app
πŸ“± Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

what-the-diff bot commented Apr 9, 2025

PR Summary

  • Integration of 'addVitePlugin' import from '@nuxt/kit'
    The team introduced the import addVitePlugin from the @nuxt/kit. This added functionality assist in enhancing the plugin handling capability of the application.

  • Inclusion of Tailwind CSS Version 4 detection mechanism
    A new check was introduced to identify if Tailwind CSS version 4 is being used. If detected and the experimental supports are not enabled, the system will now provide a warning to the user.

  • Modification of 'resolveCSSPath' for Tailwind CSS Version 4 support
    The resolveCSSPath was modified to support Tailwind CSS version 4. If the resolution fails, it has been designed to generate a default CSS file automatically for Tailwind CSS 4.

  • Conditional addition of Vite plugin for Tailwind CSS
    New logic was added to add the Vite plugin for Tailwind CSS only under specific conditions: if the builder is @nuxt/vite-builder and Tailwind 4 is detected.

  • Upgrade of PostCSS plugin handling
    The PostCSS plugin handling system was updated. If Tailwind CSS version 4 is detected, the system will support it, otherwise it will revert back to the previous configurations.

  • Extension of 'ExperimentalOptions' type
    The ExperimentalOptions type was expanded to include a new tailwindcss4 option. This will allow users to leverage the capabilities of Tailwind CSS 4 within the application.

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.

1 participant