When attempting to utilize Tailwind’s arbitrary variants syntax, hugo_stats.json seems to encode the & and >, and breaks Tailwind’s ability to recognize these classes in and build the rules.
E.g. a class of [&:nth-child(2)>figcaption]:bg-black results in "[\u0026:nth-child(2)\u003efigcaption]:bg-black", in huto_stats.json.