v2.2.5 not generating global variables

[mrtnbroder]

What version of Tailwind CSS are you using?

v2.2.5

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

nextjs v11

What version of Node.js are you using?

14

What browser are you using?

Chrome

What operating system are you using?

macOS

Reproduction repository

https://codesandbox.io/s/modest-morning-53dm6?file=/src/styles/index.css

Describe your issue

After upgrading to the latest patch version, it seems like there is now a bug with the transform property. the CSS being generated:

position: absolute;
top: 0px;
right: 0px;
--tw-translate-x: -0.875rem;
transform: var(--tw-transform);
--tw-translate-y: 0.875rem;
transform: var(--tw-transform);

as you can see, it generated --tw-translate-y and --tw-translate-x but tries to use --tw-transform which is not available or set anywhere.

This is how it's being generated:

.class {
  @apply absolute top-0 right-0 -translate-x-3.5 translate-y-3.5;
}

UPDATE:

Sorry, i just downgraded and see that it's actually because it's not generating variables for *, ::after, ::before

  // this is missing in 2.2.5
*, ::before, ::after {
  ...
  --tw-transform: translateX(var(--tw-translate-x)) translateY(var(--tw-translate-y)) rotate(var(--tw-rotate)) skewX(var(--tw-skew-x)) skewY(var(--tw-skew-y)) scaleX(var(--tw-scale-x)) scaleY(var(--tw-scale-y));
  ...
}

[adamwathan]

Hey! Please provide a reproduction repository, this behavior has changed (with JIT only) but is still intended to work, just works differently now:

#4850

This is in production on tailwindcss.com and all transforms and stuff are working correctly there so there must be something else contributing that isn't captured in this issue.

[mrtnbroder]

@adamwathan here you go: https://codesandbox.io/s/modest-morning-53dm6?file=/src/styles/index.css

If you inspect the button element, you'll see the bug I described above.

[adamwathan]

Should be fixed in v2.2.6, thank you for helping me find this one!

[mrtnbroder]

Thank you!

[mattiaz9]

I still have this problem with tailwind 2.2.6 using vite and JIT. Downgrading to 2.2.4 fixed it.

[adamwathan]

@mattiaz9 Please open a new issue with a reproduction.