fix(schema): use rootDir
rather than process.cwd
for modulesDir
#25766
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 #25408
β Type of change
π Description
This addresses a number of schema issues.
fs.allow
andmodulesDir
arrays.<srcDir>
and<workspaceDir>
aliases to clean up generated documentationprocess.cwd()
to modulesDir but instead rootDir (which defaults toprocess.cwd()
if no value is provided). This is the most significant change and means that Nuxt's behaviour will change when runningnuxi some/directory
. It will no longer pull in thenode_modules
from the directory where you are running nuxi but will instead pull in thenode_modules
from the Nuxt project you are running, which seems to be the better behaviour.I wonder if the
π Checklist