next-with-linaria and tsconfig paths

[altano]

When I add withLinaria to my next.config.ts, all files that use tsconfig paths start spitting out errors about modules not being found.

Can you think of any reason withLinaria would break the usage of tsconfig paths?

[dlehmhus]

Hey @altano, unfortunately that issue doesn't sound familiar to me. Could you provide a minimal reproducible example?

[Yabes]

Hello, I encountered a similar issue. I have a lot of errors, but my application still works. Could it that in transformLoader:72 you added a console.error(...) where it was absent in the original linaria webpack5 loader?