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

JIT stops compiling on error in imported files when watching #4904

Closed
andershagbard opened this issue Jul 6, 2021 · 1 comment · Fixed by #5249
Closed

JIT stops compiling on error in imported files when watching #4904

andershagbard opened this issue Jul 6, 2021 · 1 comment · Fixed by #5249

Comments

@andershagbard
Copy link

What version of Tailwind CSS are you using?

2.2.4

What build tool (or framework if it abstracts the build tool) are you using?

webpack 5

What version of Node.js are you using?

14.16.1

What browser are you using?

N/A

What operating system are you using?

macOS

Reproduction repository

https://github.com/andershagbard/tailwind-error

Describe your issue

This is a little complex, and I may get things wrong. This is my understanding of the problem by debugging.

My error is when I run yarn watch (webpack --mode development --watch --progress)

When I make an error in the file, e.g. forgetting to close a class. The compiler then returns and error. I correct this error and it recompiles.

When I make an error in @apply. This could be adding a background which doesn't exists, it returns an error as expected, but when I correct the error, it does not recompile. I have to restart the watch command to get it running again.

  • This error only happens when I have imported a CSS file. E.g. scaffolding.css
  • This error doesn't happen when i remove tailwindcss/nesting from postcss.config.js

I hope this information is enough to debug this further.

@adamwathan
Copy link
Member

Will be fixed in the next patch release, hopefully get it out early next week 👍🏻 Thanks!

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 a pull request may close this issue.

2 participants