feat(nuxt): skip the root uno.config
when merging
#3886
Merged
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.
Related #3837
#3838 added logic to merge ALL
uno.config
s from Nuxt layers and generate./.nuxt/uno.config.mjs
.Problem:
Because Eslint, VSCode plugins and other tools rely on
uno.config
file, we need to tell them to look for the new location(./.nuxt
). While this can be done for Eslint (settings->unocss->configPath), implementing a new option for VSCode, JetBrains etc. will kill DX.This PR skips the root
uno.config
file when merging configs from Nuxt layers, so user should manually reexport merged config from./.nuxt/uno.config.mjs
and other tools will work as usual: