fix(nuxt): include external layers in tsconfig.json
scope
#21917
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
#21877
β Type of change
Not sure which type(s) apply.
π Description
Volar 1.8.2 introduced a breaking change regarding the way it handles
tsconfig
.Until this PR, we needed to manually add our layer(s) paths to the
include
section, that'd override the default one, on our projecttsconfig
to get support for things like autocompletion. Something like:What this PR does is check
nuxt.options._layers
for paths that are different thannuxt.options.rootDir
and add them, with a trailing**/*
to theinclude
array, next to./nuxt.d.ts
and all the other ones.There's probably a better way to do it, but it works for now.
π Checklist
I don't think documentation should mention it, as it's transparent for the user like the rest of the
tsconfig
file.