fix(e2e): detect nuxt config files in .config
folder
#1381
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
Resolves #893
β Type of change
π Description
Some people are using the
.config
folder alternative for projects with many configuration files, and sincec12
fromunjs
andnuxt
itself support.config
folder would be nice to be able run tests using this alternative :)Added support for detecting Nuxt apps that use config files inside the
.config
folder. I hardcoded the possible resolvable configs following the same pattern as the existing for default config files. No need to setcoonfigFile
optionAlso added a
dot-config
test fixture inexamples/module/test/fixtures