-
Notifications
You must be signed in to change notification settings - Fork 183
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
chore(deps): Update tailwind to 2.1 to natively support JIT #326
Conversation
Codecov Report
@@ Coverage Diff @@
## main #326 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 37 41 +4
Branches 8 9 +1
=========================================
+ Hits 37 41 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update src\index.ts
to reflect changes
@atinux |
Updated and merged, thank you very much ❤️ |
Hi there!
TailwindCSS team added the JIT mode to the core!
Some issues could probably resolve itself if we stop using the additional jit true/false config and let the process be more fluid #299, #298, #302 .
Since the JIT mode needs "a basic" purge config for now (an array referring files to watch instead of a object containing a content property), I also updated the documentation to make it clear that we need to override the default nuxtjs-tailwind purge config from this:
to this:
I would like to add some test for this, but I'm not so comfortable with Jest to analyze the javascript compilated file to expect the
top-[12px]
class to be present in it.