You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is caused by the fact that vuetify has a peer dependency on vue-i18n@^9.0.0, while the root project has a dependency on vue-i18n@^8.25.1. This causes a conflict between the two versions of vue-i18n and the installation fails;
Using --force or --legacy-peer-deps flags is not a good solution, as it may lead to potential issues in the future AND/OR may not be an option for all dev/prod servers;
Vuetify cannot be considered as an option fur our projects because of that;
The text was updated successfully, but these errors were encountered:
It just means that if it's installed it should match a certain range, they aren't necessarily using any code that interfaces between vue-i18n and vuetify though.
vue-i18n@8.x.x does work with Vue 3. We're already using it in some Vue 3 projects.
The reason why we couldn't upgrade to vue-i18n@9.x.x is that it's no longer supporting custom formatters which we make an extensive use of in our projects. According to their documentation, this feature will only be re-implemented in next major release.
KaelWD
added
T: bug
Functionality that does not work as intended/expected
framework
Issues and Feature Requests that have needs framework-wide.
labels
Aug 17, 2024
Environment
Vuetify Version: 3.5.17
Vue Version: 3.4.26
Browsers: Chrome 124.0.0.0
OS: Mac OS 10.15.7
Steps to reproduce
npm
;npm i vuetify
in terminal;Expected Behavior
Vuetify should be installed without any issues;
Actual Behavior
Vuetify installation fails with the following error:
Reproduction Link
https://github.com/pcoterecollective/vuetify-issue
Other comments
vuetify
has a peer dependency onvue-i18n@^9.0.0
, while the root project has a dependency onvue-i18n@^8.25.1
. This causes a conflict between the two versions ofvue-i18n
and the installation fails;--force
or--legacy-peer-deps
flags is not a good solution, as it may lead to potential issues in the future AND/OR may not be an option for all dev/prod servers;The text was updated successfully, but these errors were encountered: