fix: support --dotenv for analyze
#589
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.
🔗 Linked issue
nuxt analyzeshould accept--dotenvflag likenuxt build#542❓ Type of change
📚 Description
Resolves #542
Not sure if bug fix or feature, but it makes sense users want to run analyze using the same options as the build command (should analyze actually be an option/flag for the build command?).
I haven't actually tested whether the env file is being used, not sure what an easy way is to check this, but I simply applied the flag the same way as in the build command.
This PR also moves the
--dot-envargs intosrc/commands/_shared.tslike other common/shared flags.