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
There is no point in doing so. The package never imports or uses @vue/composition-api in any other way. As such, @vue/composition-api should not be listed as a dependency.
Having it pulls unnecessary libraries in Vue 3 projects and pollutes output with warnings:
WARN Issues with peer dependencies found
.
└─┬ @vue/composition-api 1.7.2
└── ✕ unmet peer vue@">= 2.5 < 2.7": found 3.4.37
The text was updated successfully, but these errors were encountered:
There is no point in doing so. The package never imports or uses @vue/composition-api in any other way. As such, @vue/composition-api should not be listed as a dependency.
Having it pulls unnecessary libraries in Vue 3 projects and pollutes output with warnings:
WARN Issues with peer dependencies found
.
└─┬ @vue/composition-api 1.7.2
└── ✕ unmet peer vue@">= 2.5 < 2.7": found 3.4.37
@IlyaSemenov
Yes, you are right. The package after building does not need "peerDependencies": {
"@vue/composition-api": "^1.0.0-rc.1",}. The reason why it exists in package.json is because this dependency is needed during development. Later, we will separate the build and dev of the code. The package after building will remove unnecessary dependencies.
@townsquarelabs/ui-vue
lists@vue/composition-api
as a peer dependency:tonconnect-ui-vue/package.json
Line 61 in ee614c6
There is no point in doing so. The package never imports or uses
@vue/composition-api
in any other way. As such,@vue/composition-api
should not be listed as a dependency.Having it pulls unnecessary libraries in Vue 3 projects and pollutes output with warnings:
The text was updated successfully, but these errors were encountered: