If I use JIT the mix watcher goes crazy

[SergiArias]

JIT works, but then, mix starts to compile and recompile obsessively when doing npm run watch, and not waiting on save. Normal mode works okey. Is there something wrong in the config? I wasn't able to find the problem.

[bakerkretzmar]

Are you using the plain starter site or one of the templates? Can you share the npm script you're running, your webpack.mix.js, and your Tailwind purge/content config?

[SergiArias]

I am using the plain starter site, without any change to webpack.mix.js. I just used mode: 'jit' in tailwind.config.js before purge.

[bakerkretzmar]

Okay thanks, what's your purge config though? Do you have a purge or content key in your Tailwind config file?

[SergiArias]

I don't, I just sticked with the out of the box config except the jit mode:

  purge: [
    'source/**/*.blade.php',
    'source/**/*.md',
    'source/**/*.html',
  ],

[keithbrink]

I recently encountered this issue and had to add TAILWIND_MODE=watch to my watch script:

"watch": "TAILWIND_MODE=watch mix watch"

[bakerkretzmar]

The Laravel Mix plugin should also be rebuilding the site. What version of laravel-mix-jigsaw are you using?

[ju5t]

I am using the latest version.

[inubayuaji]

Hey I got same issue from original post. I use tailwind 3.

[medilies]

@inubayuaji Check this readme I made for myself https://github.com/elaborate-code/elaborate-code.github.io#using-tailwind-3 it may help. And I may change its content in the futur

[inubayuaji]

Hey @medilies thanks for the kind reply
Now I managed to find the solution, I change from this code

  purge: [
    'source/**/*.blade.php',
    'source/**/*.md',
    'source/**/*.html',
  ],

to this code

content: [
    "source/_components/**/*.blade.php",
    "source/_layouts/**/*.blade.php",
    "source/_posts/**/*.md",
    "source/_posts/**/*.blade.php",
    "source/paket/**/*.blade.php",
    "source/blog.blade.php",
    "source/index.blade.php",
  ],

What I did was omit the path to the assets folder. I noticed that when the contents of the assets changed it would call the build process again, resulting in an endless loop.