Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stylistic rules do not apply #412

Closed
zecar opened this issue Apr 26, 2024 · 1 comment
Closed

Stylistic rules do not apply #412

zecar opened this issue Apr 26, 2024 · 1 comment

Comments

@zecar
Copy link

zecar commented Apr 26, 2024

Environment

  • Operating System: Darwin
  • Node Version: v20.12.2
  • Nuxt Version: 3.11.2
  • CLI Version: 3.11.1
  • Nitro Version: 2.9.6
  • Package Manager: pnpm@8.15.6
  • Builder: -
  • User Config: srcDir, devtools, components, modules, eslint, ignore, appConfig, css, extensions, ssr, routeRules, vue, nitro, runtimeConfig, auth, colorMode, router, csurf, content
  • Runtime Modules: @nuxt/eslint@0.3.10, @nuxt/test-utils/module@3.12.1, @unocss/nuxt@0.59.4, @sidebase/nuxt-auth@0.7.2, @nuxt/ui@2.15.2, @pinia/nuxt@0.5.1, @nuxt/content@2.12.1, nuxt-csurf@1.5.2
  • Build Modules: -

Package

@nuxt/eslint

Reproduction

{
eslint: {
    config: {
      stylistic: {
        indent: 2,
        quotes: 'single',
        semi: false,
        commaDangle: 'never',
      },
    },
  },
}

Describe the bug

i've just installed the @nuxt/eslint module and put this config in nuxt.config.ts

when I run eslint nuxt.config.ts nothing changes.. commaDongle is still present, semi-colon is still there

Additional context

eslint.config.mjs

import withNuxt from './.nuxt/eslint.config.mjs'

export default withNuxt({
  "rules": {
    "vue/multi-word-component-names": "off",
    "no-case-declarations": "warn",
    "no-console": "off",
    "vue/no-multiple-template-root": "off",
    "no-unused-expressions": "off",
    "@typescript-eslint/no-unused-vars": "warn"
  }
})

Logs

No response

@antfu
Copy link
Member

antfu commented Apr 29, 2024

We temporarily closed this due to the lack of enough information. We could not identify whether it was a bug or a userland misconfiguration with the given info.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required

@antfu antfu closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants