Skip to content
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

Upgrading to Tailwind CSS 2.2.0 causes infinite loop when watching for changes #32

Closed
dapunkt opened this issue Jun 18, 2021 · 7 comments

Comments

@dapunkt
Copy link

dapunkt commented Jun 18, 2021

When I now 'npm run watch', i get an infinite loop, any idea what is changed?

@jeffreyvr jeffreyvr changed the title Upgraded tailwindcss to 2.2 Upgrading to Tailwind CSS causes infinite loop when watching for changes Jun 18, 2021
@jeffreyvr jeffreyvr changed the title Upgrading to Tailwind CSS causes infinite loop when watching for changes Upgrading to Tailwind CSS 2.2.0 causes infinite loop when watching for changes Jun 18, 2021
@jeffreyvr
Copy link
Owner

jeffreyvr commented Jun 18, 2021

Upgrading to Tailwind CSS 2.2.0 seems to be causing an infinite loop when running npx mix watch / npm run watch.

Not yet sure why this is yet.

Edit 1:
When the purge option is removed from tailwind.config.js the infinite loop stops.

@danieledistanio
Copy link

FYI it is happening to me as well with a different theme/setup.

@jeffreyvr
Copy link
Owner

Thanks @danieledistanio. I've just created an issue at the Tailwind CSS repository. tailwindlabs/tailwindcss#4691

@danieledistanio
Copy link

Adam replied, in my case the issue is having:

'./*.php'

in the purge list, removing that fixes it.

@jeffreyvr
Copy link
Owner

@danieledistanio Jep, that resolves it for me too. Moving to Tailwind CSS 2.2.0 we probably need to be more specific with our purge css options.

@jeffreyvr
Copy link
Owner

Fixed by a more specific purge configuration in TailPress 0.1.1..

@jeffreyvr
Copy link
Owner

In 1.0.0 you can put your template files (header.php, single.php etc.) in a subfolder which will allow you to use wildcards again and fixes this issue.

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

No branches or pull requests

3 participants