fix(module): regression add module not updating nuxt.config
#717
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
Had a feeling this was not (fully) working, and was reminded to check it out when the functionality was mentioned during the ecosystem meeting π
Fixes a regression possibly introduced in #208, it seems like it has gone unreported all this time:
If a module had to be installed as dependency, it would exit before updating the
nuxt.config
. Since we're checking ifaddDependency
returnstrue
while it's avoid
function (see https://github.com/nuxt/cli/blob/main/packages/nuxi/src/commands/module/add.ts#L148).Not sure why we're not using
try...catch
blocks, this fix simply adds a.then(() => true)
in the interest of keeping changes small/consistent (but also because I'm not sure how to trigger/test thecatch
case π€).