Daniel Roe

This is an issue with how eslint is being configured. Have you considered using https://eslint.nuxt.com which makes sure to point eslint to the correct types?

You are overriding the typescript processor/parser. When you remove that, it works fine: ```diff - import tseslint from 'typescript-eslint'; - import vueParser from 'vue-eslint-parser'; import withNuxt from './.nuxt/eslint.config.mjs'; export default...

Ah - investigated further and I see what you mean... these rules aren't enabled by default. cc: @antfu

I will investigate this. For now, you can try working around the issue in production by explicitly setting `NODE_ENV=production` when running your app.

If you are having the problem on production, even with explicitly setting `NODE_ENV`, would you please provide a reproduction? 🙏

The issue in v3.12.1 is hopefully resolved in https://github.com/nuxt/nuxt/pull/27487 and should be in the next patch. **Workaround for prod apps:** > For now, you can try working around the issue...

Would you see if you can reproduce with just that module and raise an issue there? 🙏 cc: @benjamincanac

Pinning the tailwind version resolves the issue. Would you raise an issue upstream in `@nuxtjs/tailwindcss`? https://github.com/nuxt-modules/tailwindcss

For the issue of duplicated CSS, see https://github.com/nuxt/nuxt/issues/21821#issuecomment-1701613422 (and we can track in that issue). However, I'd like to keep this issue open to track the reported performance regression with...

~~I would love to look into this but I do need a reproduction 🙏~~ (It's likely a vite issue, but we may be able to add a hotfix in Nuxt.)