Robert Patrick

Still busted and no one cares

@richard-cox any thoughts on this? Are we missing something obvious?

@ricardogobbosouza We are seeing the same issue. While this also happens in earlier versions of Nuxt (e.g., 3.7.1), it is less noticable due to the way output is being written...

@andrejp6k That's sort of beside the point. Yes, it is possible to prevent lint from running at startup but the point of this issue is that we want to run...

@andrejp6k Sorry, seeing your config made me focus on the `lintOnStartup: false` when in fact, setting `cache: false` does seem to eliminate this behavior. It works in a dedicated eslint...

@paul-asvb Even using the nitro config above, it still doesn't work. ``` export default defineNuxtConfig({ devtools: { enabled: true }, modules: [ '@nuxtjs/proxy', '@nuxt/devtools', '@nuxtjs/i18n', '@nuxtjs/eslint-module', ], ... nitro: {...

yeah, this module is irrelevant for Nuxt 3. Just use the nitro proxy and don't look back.

It all seems relatively straightforward. The last step is the only tricky one - Convert createNitroApp into an async function that returns `Promise` - Change the plugin invocations to catch...

are we waiting on something specific to review and merge this fix?  Seems like a simple fix for a critical issue...

> I'm wondering why this change? There are different Escape modes, have you tried the `DoubleQuote` escape mode... I don't see how the refenced issue is solved, there's no tests...