Closed damien-biasotto closed 6 years ago
Thanks for the PR!
Well, I think it may be the case to add buefy to peerDependencies
and let the user install the version he wants.
{
....
"peerDependencies": {
"buefy": "^0.x"
}
}
Thoughts about it?
Hmm, I would personally increment the buefy version simultaneously with every nuxt-buefy release. This way you know that everything works together. For example when someone wants to use an older buefy version but the nuxt-module is optimised for the newest version you have no easy way of making them work together.
I would propose to increment the buefy dependency and bump the version number of the nuxt module whenever buefy gets updated.
For example: nuxt-buefy: 0.0.4 buefy: 0.6.5
next update:
nuxt-buefy: 0.0.5 buefy: 0.6.6
Buefy released version 0.7.5 https://github.com/buefy/buefy/releases/tag/v0.7.5
Fix issue #6.