fix(cleanup): remove dev buildDir, not production #590
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
β Type of change
π Description
Resolves #533
It seems like, after running the dev server when using
compatibilityVersion: 4, loading the nuxt config will no longer give the configuredbuildDirwhich will instead be set to something like/node_modules/.cache/nuxt/.nuxt. This is not very useful as we're already clearing the/node_modules/.cachedirectory with this command.I'm not entirely sure what causes this change, but I did find that passing
overrides: { dev: true }toloadNuxtConfigreturns the expected values, not sure if this has other unintended consequences, we're only using therootDirandbuildDirfrom the loaded config.