Next.js dev and prod build stuck in infinite loop since 2.4.2

[berndartmueller]

Hey guys,

I'm having a hard time figuring out why my project (Next.js 10.1.4-canary.10, Preact, linaria) build is stuck in an infinite loop since upgrading from twin.macro 2.4.1 to 2.4.2.

Does someone else have similar issues?

Thanks a lot!

[ben-rogerson]

Are you seeing any console errors that would help track down the bug?

Twin doesn't officially support Linaria yet so I'd need to see a reduced test case to look into this further (no existing examples to test with).

[ben-rogerson]

hey Bernd, I pulled down that example, fixed the types file and had no issues with the build / dev.
Did you find out what combination of classes would cause the issue?

[berndartmueller]

I was not able to replicate the issue with my code example. As I said in my previous comment, it seems to be caused by having a large page with many tailwindcss classes.

Maybe you can replicate it by artificially blowing up the to be processed tailwind classes during the build.

If I can be of any help, let me know!

[berndartmueller]

@ben-rogerson Are you making any progress on this issue? Is there anything that prevents you from rewriting this normalizeUserPluginSelectors () to use a for loop instead of reduce()?

[ben-rogerson]

No progress yet, last time I looked at this I was unable to reproduce the issue.

I loaded up your example with enough plugin classes to bloat the build to 2+ minutes and couldn't reproduce the issue.

Can you perhaps duplicate your project and whittle it down to a minimal reproduction I can test with?

[berndartmueller]

Weird.

Ok I’ll try my best to reproduce it in a separate repository.