Skip to content

Commit

Permalink
fix: start script to work with tailwind jit
Browse files Browse the repository at this point in the history
  • Loading branch information
@timlrx
timlrx committed May 25, 2021
1 parent 9b04263 commit 3c3cb9c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion package.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"version": "0.3.3",
"private": true,
"scripts": {
"start": "next-remote-watch data/blog --root . -p",
"start": "cross-env TAILWIND_MODE=watch next-remote-watch ./data",
"dev": "cross-env TAILWIND_MODE=watch next dev",
"build": "next build && node ./scripts/generate-sitemap",
"serve": "next start",
Expand Down

4 comments on commit 3c3cb9c

@vercel
Copy link

@vercel vercel bot commented on 3c3cb9c May 25, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

@DoctorDerek
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW enabling watch mode didn't fix my issue with jit occasionally not working; there is discussion in tailwindlabs/tailwindcss#4081

@timlrx
Copy link
Owner Author

@timlrx timlrx commented on 3c3cb9c May 26, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing me to the issue! I was searching it for an open issue and could not find one. Yes, agree that the solution is flaky. You still need to add the env variable for it to work but somethings it just breaks and if so I find modifying the tailwind config file or deleting the .next folder "fixes" it.

@DoctorDerek
Copy link
Contributor

@DoctorDerek DoctorDerek commented on 3c3cb9c May 26, 2021 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.