Skip to content
This repository was archived by the owner on Feb 14, 2022. It is now read-only.

Commit 0729666

Browse files
committed
Add note to JIT post
1 parent 7cdfe39 commit 0729666

File tree

1 file changed

+2
-0
lines changed
  • src/pages/just-in-time-the-next-generation-of-tailwind-css

1 file changed

+2
-0
lines changed

src/pages/just-in-time-the-next-generation-of-tailwind-css/index.mdx

+2
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ export const meta = {
1717
`,
1818
}
1919

20+
_**Update**: As of Tailwind CSS v2.1, the new Just-in-Time engine is included right in Tailwind CSS itself, so you don't need the `@tailwindcss/jit` package anymore. [Learn more in the documentation](https://tailwindcss.com/docs/just-in-time-mode)._
21+
2022
One of the hardest constraints we've had to deal with as we've improved Tailwind CSS over the years is the generated file size in development. With enough customizations to your config file, the generated CSS can reach 10mb or more, and there's only so much CSS that build tools and even the browser itself will comfortably tolerate.
2123

2224
For that reason, you've always had to be careful about expensive changes to your config file like adding too many extra breakpoints or enabling extra variants like `disabled` or `focus-visible`.

0 commit comments

Comments
 (0)