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

Problem with Nuxt Playground linting #501

Open
GaborTorma opened this issue Sep 21, 2024 · 0 comments
Open

Problem with Nuxt Playground linting #501

GaborTorma opened this issue Sep 21, 2024 · 0 comments

Comments

@GaborTorma
Copy link

GaborTorma commented Sep 21, 2024

Environment


  • Operating System: Linux
  • Node Version: v22.8.0
  • Nuxt Version: 3.13.2
  • CLI Version: 3.13.2
  • Nitro Version: 2.9.7
  • Package Manager: [email protected]
  • Builder: -
  • User Config: devtools
  • Runtime Modules: -
  • Build Modules: -

Base repo from nuxt layer template with the following command:
npx nuxi init --template layer nuxt-layer

Package

@nuxt/eslint

Reproduction

https://stackblitz.com/~/github.com/GaborTorma/nuxt-eslint-playground-error

You need to see on the console. Lint automatically runs.

Describe the bug

1. vue/multi-word-component-name rule

Default this off on nuxt pages and layers folder, but it not working in .playground folder.

pages/index.vue has no error, but the same file in playground (.playground/pages/index.vue) has error.

2. vue/no-multiple-template-root rule

Default this is error on nuxt pages and layers folder, but it not working in .playground folder.

pages/multiple-template-root.vue has error, but the same file in playground (.playground/pages/multiple-template-root.vue) has no error.

Additional context

The problem is the nuxt/disables/routes and nuxt/vue/single-root use a generated files path instead of using a general glob path.
2024-09-21_13-23-01
The right one is the following:
2024-09-21_13-24-49

Logs

2024-09-21_13-27-51

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

1 participant