refactor: #815 shadcn-nuxt dependencies and CLI init #821
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.
Closes: #815
π Linked issue
This pull request is intended to close issue number #815
β Type of change
π Description
This pull request intends to do two things namely:
PROJECT_DEPENDENCIES
object had two properties namely:base
andnuxt
but now it only has thebase
as its property. In thebase
array we have 5 dependencies that get installed when initializing the Shadcn Vue CLI as long as the framework selected is not Nuxt. In thenuxt
array we only had the@nuxtjs/tailwindcss
module which got installed if you selectednuxt
as your preferred framework but this doesn't look right because we could install this alongside theshadcn-nuxt
module allowing for separation of concerns. This PR intends to fix this issue by allowing the dependencies in thebase
array to be installed in all the frameworks includingNuxt
because the issue raised here states that theshadcn-nuxt
module doesn't install any dependencies. This PR intends to fix that.shadcn-nuxt
module: This PR intends to refactor theshadcn-nuxt
module by installing the required modules (@nuxtjs/color-mode
and@nuxtjs/tailwindcss
) and thus allows for the separation of concerns between the module and the CLI. In simple terms, the CLI handles general functionalities while the module ( shadcn-nuxt ) handles specific functionalities related to Nuxt.πΈ Screenshots (if appropriate)
π Checklist