feat: allow config key sorting on files not named nuxt.config
#630
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.
π Linked issue
resolves #606
β Type of change
π Description
Currently, the
nuxt-sort-config-keysrule only applies to a file namednuxt.config.{ts,js,mts,mjs,tsx,jsx}. This prevents people from using the rule to sort config files they may extract from the main Nuxt config due to e.g. file size. The rule is updated to remove the early return when the filename does not matchnuxt.config.{ts,js,mts,mjs,tsx,jsx}.As Nuxt supports the config-dir proposal, the default setup for
nuxt/sort-confighas been expanded to support.config/nuxt.{ts,js,mts,mjs,tsx,jsx}as well, following conventions from the proposal. Any other filename may be easily added using a user's own ESLint config.