This repository was archived by the owner on Apr 6, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 41
Purge option is causing webpack to not finish #98
Comments
Hey! You need to set TAILWIND_MODE=build if you are trying to do one off builds in development. We have to run some background watch processes and we can't reliably detect one off builds vs watchers to know if we should run them or not, so by default we assume you're running a watcher if NODE_ENV=development. Eventually we'll probably move this to the config file instead of an env variable 👍🏻 |
Is this for every build? Dev or production? |
Something like this?
|
Yep that's exactly right, should do it! |
Going to close because this is covered in the README but happy to help still if you run into any snags 👍🏻 |
I can confirm it's working now and it was covered in the readme |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First of all - great work guys! I am already a fan of tailwindcss and bought the tailwindui and I am loving it.
I switched to jit compiler but it is causing a strange behaviour - webpack compiled successfully, but it's not finishing the process.
Steps to reproduce:
laravel new tailwindcss
npm install
npm install laravel-mix --save-dev
npm install -D tailwindcss@latest postcss@latest autoprefixer@latest
npx tailwindcss init
npx tailwindcss init
npm run dev
npm install -D @tailwindcss/jit tailwindcss postcss autoprefixer
The text was updated successfully, but these errors were encountered: