docs: remove @nuxtjs/eslint-config* fragments
#302
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've opened #303 to provide some clarity on this. Help is very welcome ❤️ (Feel free to DM me if you have any questions.) |
|
Closing this, having an eye on #303 and hopefully giving a helping hand. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There seems to be much confusion around the new namespace for this config.
I also got confused when evaluating the new ESLint config for our internal Nuxt 3 template.
I would like to help to clarify the current
mainreadme respectively the@nuxt/eslint-configs readme in this draft. Maybe you can chime in @danielroe and give some direction?