Alexander Kachkaev

Happy to make additional changes if needed. What would you suggest?

It's probably an issue with TailwindCSS itself: https://github.com/tailwindlabs/tailwindcss/issues/15005

I think that the rule is triggering correctly. It matches the list of property _names_ rather than names and values. If we set, say: ```css .foo { background: red }...

I can confirm a new issue in Next.js (Pages router) and 0.6.3: ``` ⚠ ./node_modules/@logtape/logtape/esm/nodeUtil.cjs Critical dependency: require function is used in a way in which dependencies cannot be statically...

👋 @dahlia! I tried `v0.6.4-dev.96` right now. Still getting this warning from Next.js webpack (on the server): ``` Critical dependency: require function is used in a way in which dependencies...

👋 @nicooprat! You should be able for that [tailwindcss/no-custom-classname](https://github.com/francoismassart/eslint-plugin-tailwindcss/blob/master/docs/rules/no-custom-classname.md) rule for that.

@blue-infinex I see two options here: 1. You can remove colors like `text-red-500` from your theme. [`tailwindcss/no-custom-classname`](https://github.com/francoismassart/eslint-plugin-tailwindcss/blob/master/docs/rules/no-custom-classname.md) will flag them but also all existing instances will stop working (all replacements...

I had this issue as well. Running `pnpm install` was a huge pain because it was spawning countless instances of `rg`. Have a look at the scrollbar size for this...

Same issue here. Cold start takes more than five seconds. To me as a user, it feels forever. Just tried opening our team’s app on Monday morning and it took...

@mxkxf are you on Amplify Gen 1 or Gen 2? I have a small hope that upgrading could help, but if you are on Gen 2 already, that’s pretty disappointing....