This PR fixes the issue about specifying dependencies to be installed with the add command fails for the Nuxt.js template irrespective of the directory client/server. The proposed fix skips from performing further configuration if the template chosen is Nuxt.js or the directory is server regardless of the template. All other starter templates have the client/src/main.js as a valid path, which wasn't the case with Nuxt.js. For the server directory, this isn't required since all configuration updates happen for dependencies relating to the client (vuex, vuetify, Nuxt modules, etc).
What kind of change does this PR introduce?
bug fix
Did you add tests for your changes?
The existing test suite accounts for it.
If relevant, did you update the documentation?
N/A
Summary
Fixes #247
This PR fixes the issue about specifying dependencies to be installed with the
addcommand fails for theNuxt.jstemplate irrespective of the directoryclient/server. The proposed fix skips from performing further configuration if the template chosen isNuxt.jsor the directory isserverregardless of the template. All other starter templates have theclient/src/main.jsas a valid path, which wasn't the case withNuxt.js. For the server directory, this isn't required since all configuration updates happen for dependencies relating to theclient(vuex,vuetify, Nuxt modules, etc).Does this PR introduce a breaking change?
No
Other information
N/A