You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tailwindcss v.2+ css rules with class name selectors also used in tailwindcss classes in combination with @apply with the same class name produces nodejs v8 fatal error
#3541
Closed
mayoujin opened this issue
Feb 7, 2021
· 1 comment
Using css rules with class selector which used in Tailwindcss version 2+ with @apply rule with the same class name explodes nodejs v8.
Such a rule (accidentally typed)
.hidden, .some-class {
@apply hidden;
}
produces fatal error which hard to detect conditions of it:
The text was updated successfully, but these errors were encountered:
mayoujin
changed the title
Css rule wih
Tailwindcss v.2+ css rules with class name selectors also used in tailwindcss in combination @apply with the same class name produces nodejs v8 fatal error
Feb 7, 2021
mayoujin
changed the title
Tailwindcss v.2+ css rules with class name selectors also used in tailwindcss in combination @apply with the same class name produces nodejs v8 fatal error
Tailwindcss v.2+ css rules with class name selectors also used in tailwindcss classes in combination with @apply with the same class name produces nodejs v8 fatal error
Feb 7, 2021
Hey! This is a circular dependency causing infinite recursion, you are trying to apply hidden to itself. Apply copies all instances of a selector and does so recursively, so this understandably blows things up.
Not sure what your desired output is in this situation but if you want to start a discussion thread explaining what you're trying to achieve happy to help there.
Describe the problem:
Using css rules with class selector which used in Tailwindcss version 2+ with @apply rule with the same class name explodes nodejs v8.
Such a rule (accidentally typed)
produces fatal error which hard to detect conditions of it:
Json report applied.
report.20210207.200910.12722.0.001.json.log
The text was updated successfully, but these errors were encountered: