chore: migrate to Nuxt ESLint

[shinGangan]

🔗 Linked issue

❓ Type of change

• [ ] 📖 Documentation (updates to the documentation or readme)
• [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
• [ ] 👌 Enhancement (improving an existing functionality)
• [ ] ✨ New feature (a non-breaking change that adds functionality)
• [x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Repositories in Nuxt oranization are migrating to use Nuxt ESLint. Therefore, this repository has also been migrated to use @nuxt/eslint-config instead of @antfu/eslint-config.

Note

node/prefer-global/process and node/prefer-global/buffer are rules provided by eslint-plugin-n, and were not provided by default in @nuxt/eslint-config.

As before, if necessary, you can configure all eslint-plugin-n rules configured in @antfu/eslint-config in a separate PR. 👍

I thought that this rules should be implemented after receiving @harlan-zw 's opinion, so it has not been addressed in this PR.

[vercel[bot]]

@shinGangan is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

[shinGangan]

Hi @harlan-zw , please review and comments when you have a time 🙏

[shinGangan]

Btw, I would like to take advantage of the monopo configuration to simplify package management in the playground/ and docs/. Is this okay to try? (I will implement this in another PR)

[harlan-zw]

Thanks! This is some great work